This is more compatible with Eclipse; Eclipse can't handle a nested project structure.
In addition, I expect that the release numbers of some of the sub-projects will "decouple". That is, tapestry-spring may become stable at, say, 5.0.4 and we'll leave it alone as we rev tapestry-core up to, say, 5.0.9. Anyway, that's the theory. The practice is looking a little different, because of JIRA. Having just TAPESTRY as the issue tracker key limits the ability to meaningfully track version numbers across the components (such as tapestry-core). One option would be to start creating sub-projects within the Tapestry category (currently, there's just the TAPESTRY project), so that each could track its bugs itself. Another option would be to re-organize it, as you mentioned, with tapestry5/trunk/tapestry-xxx and tapestry/tags/tapestry-xxx ... that would certainly make things easier when creating a new release (much less tagging!). SVN does let us change our mind after the fact, to a large degree. On 3/14/07, Dan Adams <[EMAIL PROTECTED]> wrote:
I noticed in the tapestry sources that while it's a multi-module maven project, all of the modules are at the same level in the source tree and each have their own set of branches/tags/trunk folders rather than having each module contained within it's parent module. What have you found to be the advantages of this? How does having each in a separate folder effect doing releases? Do you keep the version numbers in sync? Thanks. :) -- Dan Adams Senior Software Engineer Interactive Factory 617.235.5857 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
