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:
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,
But when you release the parent, do you also release all the submodules or do
you run mvn with non-recursive?
With regards,
Nick Stolwijk
-Original Message-
From: Jochen Wiedmann [mailto:[EMAIL PROTECTED]
Sent: Mon 1/21/2008 10:52 AM
To: Maven Users List
Subject: Re: Best practices
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. To
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. But if you use the release plugin to release the parent,
will the tag contain only the parent or all the submodules
In my opinion, trunk is the development version aka SNAPSHOT. Only the tags
should contain the released version number. Each module should provide the
parent version it needs and can only be released if that is a non-SNAPSHOT
version.
With regards,
Nick Stolwijk
-Original Message-
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
