You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/22 12:16:00 UTC

[jira] [Resolved] (MRELEASE-824) Allow update of artifact-versions of dependencies that are currently not in the maven reactor

     [ https://issues.apache.org/jira/browse/MRELEASE-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliotte Rusty Harold resolved MRELEASE-824.
--------------------------------------------
    Resolution: Won't Do

> 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
(v8.3.4#803005)