[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 closed MRELEASE-734.
---
Resolution: Fixed
Fixed in [r1385048|http://svn.apache.org/viewvc?rev=1385048view=rev]
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
[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
[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:
Component/s: prepare
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
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
[jira] (MRELEASE-734) When releaseVersion and developmentVersion are passed in command-line but are empty should be treated as not-defined
Dmitry Katsubo created MRELEASE-734:
---
Summary: 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
Affects Versions: 2.2.2
Reporter: Dmitry Katsubo
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
