maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stijn de Reede (JIRA)" <>
Subject [jira] Commented: (MRELEASE-252) Support for multi modules project
Date Wed, 25 Feb 2009 14:20:19 GMT


Stijn de Reede commented on MRELEASE-252:


This is also a becoming a major issue for our development team. We're developing components
for an ECM application. The multimodule project defines set of components linked together
to be installed in a certain environment. When we update a single component, we want to make
a new release of the multimodule project to be deployed to the Test environment. However,
if we update a single component (=submodule) and release the multimodule project, every other
component in it is also released and has it's version number updated.

Actually, the behavior I quickly thought of would be like this:

- create an option like releaseUnchangedModules=false (defaults to true)

- when you would run "mvn release:prepare release:perform" in a multimodule project, by default
the release plugin would update the version number of each module from x-SNAPSHOT to x, do
a release and set the new trunk version to (x+1)-SNAPSHOT. The aggregating project's version
would also updated.

- when you do  "mvn release:prepare release:perform -DreleaseUnchangedModules=false", the
release plugin could compare each module with the latest version in SCM. If the module hasn't
changed, the version is set back from x-SNAPSHOT to (x-1). If it has changed, it is set to
x. The new trunk version would be x-SNAPSHOT (unchanged) and (x+1)-SNAPSHOT (changed), respectively.
The aggregating project's version would also updated.

> Support for multi modules project
> ---------------------------------
>                 Key: MRELEASE-252
>                 URL:
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>          Components: perform, prepare, stage
>    Affects Versions: 2.0-beta-6
>         Environment: Maven 2.0.6
>            Reporter: Franck HUGOT
> I would like to prepare a release for multi-modules project.
> I would create tags for all the modules and modify poms.
> Not only the versionId in the pom but also the eventual dependencies between all the
> Indeed, if a module A has a dependency to module B, the version will be updated.
> The dependency management is a hard task in multi modules project and this feature would
be really appreciated.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message