> * The proposed directories are meant to reside in the current myfaces > root, right? So we would get > http://svn.apache.org/repos/asf/myfaces/current > http://svn.apache.org/repos/asf/myfaces/core > http://svn.apache.org/repos/asf/myfaces/sandbox > and so on. Correct?
Correct > * What about the current directories "branches", "tags", "trunck" and > "trunk". Any chance to get rid of them later? We might want to get rid of the existing branches stuff because AFAIK there are no legitimate branches worth saving. I know at least one of them was created by Oliver and I when we started the tree2 stuff but we never ended up using it. Now would be a good time to eliminate the other branches if we thought they were bogus. Trunck was just created by Bill Dudney. We should ask him what that was for. We would still have a branches,tags and trunk but they would reside inside of core, tomahawk, sandbox, etc (see Struts svn.) In the subprojects the branches folders would be mostly empty unless we decided to create a branch for some reason. I imagine the version folders of the tomahawk subproject would contain versions as we go forward (ex. myfaces_tomahawk_1_1_0rc2.) For other subprojects, like sandbox, they would probably never be used. That is one of the cool advantages of the subprojects, we can create branches or labels on just the portion of the code that we need. (May come in handy if we eventually have a 1.1 and 1.2 implementation of stuff.) > * How is the current link functioning? What exactly do I get when I > check out? Isn't there an awkward overlap between the examples, > sandbox and tomahawk src dir? You will get everything that is "linked" to current. Basically we would link the trunk version of everything in the top level. The branches and merge stuff would be moved to the subproject level so you don't get that stuff. So you would get core/trunk, tomahawk/trunk, etc. Except in your checkout dir it would just be myfaces/core, myfaces/tomahawk (no trunk dir.) Checkout myfaces/current and see what I mean. Also, James Mitchell said he is going to work up a Wiki on svn:externals for us. > * How will the build-script(s) be organized? Some ant targets will > only function properly when I check out the "current" tree, so that > everything is on the right place. Is that correct? Or is there a way > to make the targets function regardless of that. There is probably a way to make the build work regardless of where you are building from. We will probaby have to get creative but I think it can be done. Certainly it will work if you checkout current and build from the toplevel build dir. You may end up having to add a property or two to local.properties if you just checkout sandbox and only want to build that. > * The xdocs subproject will need a (virtual) build dir, too, I think. Hmmm. Hadn't thought about that. We might want to keep it all together just to keep it simpler. The xdocs aren't really for the users, they are just used to build the website. > Regarding share: I also have the feeling that the "right" place is the > core subproject. So I agree that the "physical" dirs should go there > and the tomahawk share should be the "virtual" dir (i.e. a link). Yes I think this will work nicely. > All in all, I'm very happy about this proposal. Thanks again, Sean. Your welcome. > -Manfred sean
