annoying indeed but you only have to set the scm urls once in the each artifact and with an archetype well only once.
i think its dumb to have the parent of several modules the same... if you think OO then the parent of any artifact should define common behaviour for articfacts of that type... so you should have a jar parent, webapp parent etc etc... and usually an aggregation of modules crosses concerns e.g. server, client, common code, persistence, api it seems really obvious to me, maybe i'm missing something On Mon, 21 Jan 2008 22:52:09 Jochen Wiedmann wrote: > On Jan 21, 2008 10:42 AM, <[EMAIL PROTECTED]> wrote: > > Is it advisable to move the commons-parent to another subdirectory or is > > this layout the preferred way? > > I was experiencing with the former, but gave it up. The reason is that > far too many plugins are not suitable to use it. Examples include: > > - The SCM URL must be configured in every subproject. Otherwise the > SCM links on the > generated site will be broken. > - The distribution URL's must be configured in every subproject. > Otherwise deployment > will use the wrong target URL. > > And so on. > > > Jochen -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
