[
http://jira.codehaus.org/browse/MRELEASE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170404#action_170404
]
Sylvain Marié commented on MRELEASE-252:
----------------------------------------
h5. Christian:
a) ??In the current release plugin, it only performs a validation to ensure
these dependencies are all release versions.??
I think that the last version is now able to update the dependency in a smarter
way: you can choose to make it update the version automatically. However the
release version must exist: you need first to release it - and this is not done
in the same process.
b) Although using the dependency graph to find projects to release might sound
appealing, it seems to me that it is against the meaning of 'dependency' vs
'module'. Indeed imagine your projects depend of each other but have their own
build cycle ; that is, they don't have a common aggregator project structure on
top of them, they are build in separate "mvn install" commands. It means that
one is a library for the other, they are not tightly coupled. They must
therefore be released in two steps: first the 'low' one then the one built on
top of it (thanks to (a)). However if you think that these projects are part of
the same build cycle (built in one "mvn install") the release plugin should be
able to release both att the same time.
> To sum up we would probably not want the maven release plugin to have to make
> a build that is more complex that what the "mvn install" build can do. We
> should play in the subset defined by the "mvn install" build IMO. Do you have
> the possibility to declare all your projects as modules of an aggregator one
> ? If so that would do the trick.
h5. Mark :
You are right about the partial tags but in my opinion it is not problematic to
TAG the whole repository, as long as the deployment of artifacts happening
during the release-perform step only focuses on the modules that were selected.
For the other modules, well the only thing that happened is that they were
tagged one extra time in the SCM: not nice, but not a big deal ?
> 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
