[MRELEASE-835] Automatically resolve snapshot dependencies in release:prepare

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.1
• Fix Version/s: 3.0.0-M4, 3.0.0-M2
• Component/s: prepare
• Flags: Patch
• Assignee: Robert Scholte
• Reporter: Thorsten Scherler
• Created: 15/Apr/13 05:30
• Updated: 19/Apr/21 10:39
• Resolved: 08/Jan/20 21:34

Description

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.

Issue Links

• is related to: MRELEASE-463 Ability to default "set to release" during release:prepare to "yes" instead of "no"
• links to: GitHub Pull Request #19