[
http://jira.codehaus.org/browse/MRELEASE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170387#action_170387
]
Sylvain Marié commented on MRELEASE-252:
----------------------------------------
Hi Christian,
I am glad to see that other development teams are faced with this issue too. I
think that most of your needs could be covered by a maven-release plugin
handling sub-modules correctly with an XML input file or an interactive
behaviour about which sub-modules should be released (see Moshe's previous
comment).
I have some doubts concerning the need for multiple root modules, though. Is it
a need that you currently have in your projects ? I mean, I think you could
just release one subtree of a root module, then one subtree of another root
module, etc. Unless you have tight snapshot dependencies between projects that
are located in separate root modules ?
Best regards,
> 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
> 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 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
