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 13:15:00 UTC
[jira] [Closed] (MRELEASE-463) Ability to default "set to release"
during release:prepare to "yes" instead of "no"
[ https://issues.apache.org/jira/browse/MRELEASE-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliotte Rusty Harold closed MRELEASE-463.
------------------------------------------
> Ability to default "set to release" during release:prepare to "yes" instead of "no"
> -----------------------------------------------------------------------------------
>
> Key: MRELEASE-463
> URL: https://issues.apache.org/jira/browse/MRELEASE-463
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: prepare
> Affects Versions: 2.0-beta-9
> Reporter: Dave Copeland
> Priority: Major
> Attachments: MRELEASE-default-snaps-PATCH.diff.gz
>
>
> We have SNAPSHOT dependencies in our poms during development. When we do a release, we use the plugin's feature of setting these versions to release before the release:prepare is done.
> This works great, however, it is not available in batch mode; the default answer is "no", and so, in batch mode, the release:prepare just fails.
> This makes scripting our releases impossible without resorting to some Expect nonsense.
> Included is a patch that adds the configuration option {{projectDependenciesDefaultToRelease}}. The value of this defaults to "false", which will cause {{release:prepare}} to behave as it does now. Setting it to "true" defaults the answer to "yes" and thus, allows the release to proceed in batch mode.
> I didn't see a lot of test coverage of this area of the code, but this patch doesn't break any tests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)