[
http://jira.codehaus.org/browse/MRELEASE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167110#action_167110
]
Sylvain Marié commented on MRELEASE-252:
----------------------------------------
To Stijn: I don't understand how moving an aggregate project to a project with
dependencies could do the trick.. You would probably need to update things by
hand then ?
To Moshe: very interesting point. In such case I thought I would not release Y
because from a code point of view it is the same. However for people compiling
against it, it prevents transitive dependency to go and pick your new release
of X so you might want to release it too to ensure that people benefit from new
version of X.
> Seems the only way is to specify what modules to release.
I totally agree. Now the question is, how ? I suggest 4 ways to do it in a
previous post ( 16/Jan/09, suggestions a),b),c),d)). Do you have other ideas ?
> 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
