[MRELEASE-463] Ability to default "set to release" during release:prepare to "yes" instead of "no"

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Do
• Affects Version/s: 2.0-beta-9
• Component/s: prepare
• Flags: Patch
• Assignee: Unassigned
• Reporter: Dave Copeland
• Created: 24/Jul/09 09:41
• Updated: 22/Dec/19 13:14
• Resolved: 22/Dec/19 13:14

Description

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.

Issue Links

• is duplicated by: MRELEASE-854 non-interactive "always yes" option
• relates to: MRELEASE-835 Automatically resolve snapshot dependencies in release:prepare