maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain MariƩ (JIRA) <>
Subject [jira] Commented: (MRELEASE-252) Support for multi modules project
Date Mon, 27 Apr 2009 12:35:45 GMT


Sylvain MariƩ commented on MRELEASE-252:

Hi everyone,

Concerning this topic we finally decided to give up and align with the "everything is a component"
layout, where 
1 SCM project(tag/trunk/branches) = 1 Maven project (1 pom of a component) and components
become independent (no aggregator pom any more). 

While this was clearly not possible for us with the old dependency mechanism (everytime a
project wasreleased, you had to update all demendencies in other projects), this is not the
case any more thanks to the scoped dependencies: a project A can depend on version [1.2,1.3)
of another project B so that releases of bug fixes in B (1.2.1, 1.2.2, ... 1.2.n) will not
impact A.

> 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