On 5/24/2012 7:39 AM, DK wrote:
Hi,
New to Maven and have a couple of questions around versioning.
Should all projects within a multi-module project have the same version?
Should all projects related to each other keep the same version number?
Any best practices on changing version numbers?
Perhaps this it not considered best practice, but we've got a lot of web
applications which are multi-module, usually a few jars/ejbs + 1-2 wars
+ ear, and I've been telling my users to let the child projects inherit
the parent project's groupId and version (i.e., the child pom specifies
the parent's groupId, artifactId and version, but only its artifactId).
A release still needs to update all the poms to update the children's
parent version, though.
IMHO, if you have a large multi-module project with a large number
subprojects that almost never change and are not build dependent on
subprojects which change frequently, it makes sense to take them out of
the multi-module project and only build them when necessary.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
