[
https://issues.apache.org/jira/browse/MRELEASE-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485977#comment-14485977
]
Robert Scholte commented on MRELEASE-824:
-----------------------------------------
Looking at the patch I'm pretty sure a lot will break. It would be better to
provide an integration-test to show the usecase and how it should be fixed. But
even then I have my doubts if I will apply it. There are already other issues
which should support more fine-grained release strategies.
> Allow update of artifact-versions of dependencies that are currently not in
> the maven reactor
> ---------------------------------------------------------------------------------------------
>
> Key: MRELEASE-824
> URL: https://issues.apache.org/jira/browse/MRELEASE-824
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: prepare
> Affects Versions: 2.4
> Reporter: Christofer Dutz
> Priority: Minor
> Attachments: release-prepare.patch
>
>
> Currently when using the default way to restrict the reactor projects
> processed by maven (using the --projects parameter), only the versions of
> artifacts currently in the reactor are updated, even if more version-data is
> passed in.
> Attachted patch allows a user to provide versions for all modules of a maven
> project, and to update only some of these. The patch shouldn't break
> anything, but it would allow to use the release plugin in special
> release-strategies that might differ from normal release strategies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
