[
http://jira.codehaus.org/browse/MRELEASE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170390#action_170390
]
Christian Gleissner commented on MRELEASE-252:
----------------------------------------------
Hi Sylvain,
thanks for your reply. I agree - we don't need to release multiple top-level
modules in a single call. However, there is an important difference between my
suggestion and Moshe's previous suggestion:
I suggest that the multi-project release plugin uses the dependency graph to
find modules to be released, rather than following module hierarchy. It would
then traverse the graph and automatically modify any dependencies from snapshot
to release versions. In the current release plugin, it only performs a
validation to ensure these dependencies are all release versions.
So there would be three key components:
- XML-based configuration to define groupId/artifactId and target release
version of all modules to be released
- Dependency graph traversal (optionally module graph traversal - not required
in our case, but may be useful)
- For each module discovered during graph traversal: Dependency adjustment from
snapshot to release before invoking release:perform, and back to the next
snapshot version afterwards
This could all be handled by either a new goal added to the existing release
plugin or by a completely new release plugin to enable decoupled development.
What do you suggest?
Thanks
Christian
> 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
