+1 for b) as if we choose a, what will be named the wrapper module containing the parent and the [EMAIL PROTECTED]
Raphaêl 2008/4/27, Dan Tran <[EMAIL PROTECTED]>: > +1 for the move and keep same artifactId ie "mojo" > > > -D > > > On Sun, Apr 27, 2008 at 11:16 AM, Benjamin Bentmann > <[EMAIL PROTECTED]> wrote: > > Greetings, > > > > My experiences with the release of the Mojo Parent POM 17 make me propose > > to move the parent stuff into a dedicated directory like illustrated below: > > > > trunk/ > > mojo/ > > mojo-parent/ <- Parent POM in here, please > > antlr3-maven-plugin/ > > ... > > xslt-maven-plugin/ > > > > Rationale: > > As Dennis just pointed out, every tag of the parent POM naturally contains > > all of the plugins because they are currently child directories of the > > parent POM base directory. Surely, SVN employs cheap copies for tags and it > > doesn't really cost disk space but every checkout of the parent POM will > > effectively require a complete checkout of the entire Mojo suite. It's not > a > > big deal but I feel it's unnecessary inconvenient. The parent POM release > > gets more and more time-consuming as we add plugins (and on Windows boxes > > the tag checkout done by the Release Plugin will happily construct paths > > with more than 256 chars and fail on them, but that's another story...). > The > > Mojo Parent has a distinct release cycle from the plugins and Maven allows > > us freedom in the relative directory path between a parent and its modules, > > why not use that? > > > > Just in case we can agree on that directory move, some name proposals for > > the directory: > > a) mojo > > b) mojo-parent > > c) parent > > > > What do you think? > > > > > > Benjamin > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
