[
http://jira.codehaus.org/browse/MRELEASE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167090#action_167090
]
Stijn de Reede commented on MRELEASE-252:
-----------------------------------------
Hi Sylvain,
I see your point, and I think this indeed might also occur with our development
cycle. Of course you could add 'overwrite' parameters, like
"-DholdbackModule=module1,module2 -DreleaseModule=module3,module4" but I don't
think that's a pretty solution. It would be workable though.
Anyway, maybe we should switch from an aggregate project structure to a project
that includes the other modules (components) as dependencies. That way, we
would also have control over which version of a component is in a release to a
target environment. Since components can be generic and be released to multiple
target environments, maybe this is the way to go for us.
> 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
