maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (MRELEASE-835) Automatically resolve snapshot dependencies in release:prepare
Date Fri, 27 Oct 2017 02:34:00 GMT


ASF GitHub Bot commented on MRELEASE-835:

olamy commented on issue #19: Fix for MRELEASE-835: Automatically resolve snapshot dependencies
in release:prepare
   @theit I'm happy with those changes. Except the lack of test. Is there anything you can
do? A plugin IT test?

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Automatically resolve snapshot dependencies in release:prepare
> --------------------------------------------------------------
>                 Key: MRELEASE-835
>                 URL:
>             Project: Maven Release Plugin
>          Issue Type: New Feature
>          Components: prepare
>    Affects Versions: 2.4.1
>            Reporter: Thorsten Scherler
>         Attachments: maven-release-plugin.patch
> 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

View raw message