Re: Best practices for seperate releases of parent and modules

2008-01-21 Thread Michael McCallum
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...

RE: Best practices for seperate releases of parent and modules

2008-01-21 Thread nicklist
- From: Jochen Wiedmann [mailto:[EMAIL PROTECTED] Sent: Mon 1/21/2008 11:58 AM To: Maven Users List Subject: Re: Best practices for seperate releases of parent and modules On Jan 21, 2008 11:48 AM, <[EMAIL PROTECTED]> wrote: > But normally the trunk should always contain a SNAPSHOT version,

Re: Best practices for seperate releases of parent and modules

2008-01-21 Thread Jochen Wiedmann
On Jan 21, 2008 11:48 AM, <[EMAIL PROTECTED]> wrote: > But normally the trunk should always contain a SNAPSHOT version, but only the > submodules don't > have it as parent as long as they don't need to rely on the changes in the > parent. I do not know, why it "should". We do not do it that way

RE: Best practices for seperate releases of parent and modules

2008-01-21 Thread nicklist
hole tree. Seems a little strange to me. With regards, Nick Stolwijk -Original Message- From: Jochen Wiedmann [mailto:[EMAIL PROTECTED] Sent: Mon 1/21/2008 11:39 AM To: Maven Users List Subject: Re: Best practices for seperate releases of parent and modules On Jan 21, 2008 11:00 AM

Re: Best practices for seperate releases of parent and modules

2008-01-21 Thread Jochen Wiedmann
On Jan 21, 2008 11:00 AM, <[EMAIL PROTECTED]> wrote: > But when you release the parent, do you also release all the submodules or do > you run mvn with non-recursive? If the parent hasn't changed (in other words, if it hasn't a SNAPSHOT version), then I am happy to release the submodules only.

RE: Best practices for seperate releases of parent and modules

2008-01-21 Thread nicklist
for seperate releases of parent and modules 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

Re: Best practices for seperate releases of parent and modules

2008-01-21 Thread Jochen Wiedmann
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 inclu

Best practices for seperate releases of parent and modules

2008-01-21 Thread nicklist
At our company we are busy with a commons project, which has a few submodules. Our current layout is: commons-parent/ commons-module-1/ pom.xml src/ commons-module-2/ commons-module-3/ pom.xml Now we want to do seperate releases of the commons-parent and the modules, just