[jira] [Updated] (MRELEASE-835) Automatically resolve snapshot dependencies in release:prepare

["Olivier Lamy (Jira)" <ji...@apache.org>]

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

Olivier Lamy updated MRELEASE-835:
----------------------------------
    Fix Version/s: 3.0.0-M4

> Automatically resolve snapshot dependencies in release:prepare
> --------------------------------------------------------------
>
>                 Key: MRELEASE-835
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-835
>             Project: Maven Release Plugin
>          Issue Type: New Feature
>          Components: prepare
>    Affects Versions: 2.4.1
>            Reporter: Thorsten Scherler
>            Assignee: Robert Scholte
>            Priority: Major
>             Fix For: 3.0.0-M4, 3.0.0-M2
>
>         Attachments: maven-release-plugin.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> mvn release:prepare has a nice feature to automatically resolve snapshot dependencies in a pom.xml when it detects that there are still unresolved ones. Unfortunately this only works in interactive mode, and directly breaks the build in batch mode.
> The attached patch adds the following two command-line parameters to release:prepare so that a user can run release:prepare in fully non-interactive mode, and doesn't change the actual behaviour when they are not given:
> * autoResolveSnapshotDependencies
> * autoResolveSnapshotDependenciesMode
> *Background:*
> Say I have projects A and B, and B depends on A. Both projects are about to be released at a certain time.
> "mvn release:prepare release:perform" does this job quite well and can be implemented for project A for example on a build server to be run non-interactively via the build server's web interface.
> To release project B in a similar way, i.e. as a non-interactive job on a build server, this requires that I manually update the snapshot dependencies of B's pom.xml and check in the modified file before I trigger the job; otherwise the build would fail.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)