You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2012/08/26 21:17:21 UTC
[jira] (MRELEASE-734) When releaseVersion and developmentVersion
are passed in command-line but are empty should be treated as not-defined
[ https://jira.codehaus.org/browse/MRELEASE-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated MRELEASE-734:
------------------------------------
Fix Version/s: 2.4
Assignee: Robert Scholte
For MRELEASE-511 this part of the code will be refactored, so this issue should be fixed as well.
> When releaseVersion and developmentVersion are passed in command-line but are empty should be treated as not-defined
> --------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-734
> URL: https://jira.codehaus.org/browse/MRELEASE-734
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
> Affects Versions: 2.2.2
> Reporter: Dmitry Katsubo
> Assignee: Robert Scholte
> Fix For: 2.4
>
>
> In my case I would like to pass {{releaseVersion}} and {{developmentVersion}} taken from user input, e.g. from [Hudson Release Plugin|http://wiki.hudson-ci.org/display/HUDSON/Release+Plugin]:
> {code}
> release:prepare release:perform -DreleaseVersion=${RELEASE_VERSION} -DdevelopmentVersion=${DEVELOPMENT_VERSION}
> {code}
> however if user leaves input fields empty it would be nice if maven-release-plugin would treat empty values as non-defined and fallback to default behaviour: inherit the next version from pom. Currently it breaks down with message 'Unable to parse the version string ""'.
--
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