[
https://issues.apache.org/jira/browse/MRELEASE-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16221991#comment-16221991
]
Robert Scholte commented on MRELEASE-835:
-----------------------------------------
I don't think this should be a {{boolean}}. I'm pretty sure you want to control
which snapshot dependencies are updated or not.
So I'd suggest to make a list of it containing versionless artifactIds with
wildcard support. For the lazy people who think it should be a boolean, they
can simply say {{\*:\*}}, which also means everything.
> 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
> 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
(v6.4.14#64029)
