[
https://jira.codehaus.org/browse/MRELEASE-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MRELEASE-269:
------------------------------------
Priority: Major (was: Trivial)
Assignee: Robert Scholte
I'm increasing the priority because I noticed that a fix for MRELEASE-511 would
slightly change the behaviour of the plugin. Up until version 2.3.2 you could
specify a snapshot as the release version from commandline. From this version
the non-snapshot version was extracted and passed as the release version. I
consider that as a bug, so with the implementation of this issue we can prevent
invalid versions.
> Check that 'new development version' is a SNAPSHOT version
> -----------------------------------------------------------
>
> Key: MRELEASE-269
> URL: https://jira.codehaus.org/browse/MRELEASE-269
> Project: Maven 2.x Release Plugin
> Issue Type: Wish
> Components: prepare
> Affects Versions: 2.0-beta-6
> Reporter: Michael Meyer
> Assignee: Robert Scholte
> Labels: contributers-welcome
> Fix For: Backlog
>
>
> While executing 'mvn release:prepare' one gets asked for the new development
> version like this:
> What is the new development version for "foo"? (com.bar:foo) 1.12-SNAPSHOT:
> Say I want the new development version to be 2.0-SNAPSHOT (and not like
> suggested 1.12-SNAPSHOT) but by accident I only enter 2.0. This will work
> just fine until I want to execute 'mvn release:prepare' again at some later
> point. Then I will get the error message that the current version is not a
> SNAPSHOT version.
> It would be really nice if release:prepare could check if I have entered a
> valid SNAPSHOT version. If not release:prepare should fail or even nicer ask
> me to enter a proper SNAPSHOT version.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
