[jira] Commented: (MRELEASE-252) Support for multi modules project

["Moshe Bergman (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MRELEASE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143588#action_143588 ] 

Moshe Bergman commented on MRELEASE-252:
----------------------------------------

I would also like the maven release plug-in, to create a tag for each module rather then the whole tree.

This way, it will also be possible to release just a single module independently of the whole project.

The way I see it, it should work like this:
Option 1 - release all modules:
1) Version of parent pom is updated and all modules as well
2) Tag is created for each module.

Option 2 - release a single module
1) Version of the parent pom is updated
2) Tag is created of the single module
3) dependency to this module is updated across all modules.

Maybe add an option to support this model?

> Support for multi modules project
> ---------------------------------
>
>                 Key: MRELEASE-252
>                 URL: http://jira.codehaus.org/browse/MRELEASE-252
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>    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 modules.
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira