[
https://issues.apache.org/jira/browse/MRELEASE-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15773065#comment-15773065
]
Luc Chapon commented on MRELEASE-951:
-------------------------------------
Hello
I don’t know how much this is related, but in my multi-module project
developmentVersion is always ignored
mvn --batch-mode release:prepare-with-pom -DreleaseVersion=9.0.21
-DdevelopmentVersion=9.0.30
I have <autoVersionSubmodules>true</autoVersionSubmodules> in my parent pom
I was expecting in my poms.xml
<version>9.0.30-SNAPSHOT</version>
or even
<version>9.0.30</version>
But I get
<version>9.0.22-SNAPSHOT</version>, which the expected value in the absence of
developmentVersion
If I go interactive, without the --batch-mode flag
These questions are asked
What is the release version for xxx 9.0.20: : 9.0.21
What is SCM release tag or label for xxx xxx-9.0.21: :
What is the new development version for xxx 9.0.22-SNAPSHOT: : 9.0.30-SNAPSHOT
and then it works !
<version>9.0.30-SNAPSHOT</version> in all my poms.xml
> Release plugin ignores release.properties developmentVersion property
> ---------------------------------------------------------------------
>
> Key: MRELEASE-951
> URL: https://issues.apache.org/jira/browse/MRELEASE-951
> Project: Maven Release Plugin
> Issue Type: Bug
> Environment: maven-release-plugin 2.5.3
> Reporter: Robert Patrick
>
> I created my release.properties file with the following content:
> tag=myproject-2.0.0
> releaseVersion=2.0.0
> developmentVersion=2.1.0-SNAPSHOT
> and invoked the release plugin with:
> mvn --batch-mode release:prepare
> After running the maven-release-plugin, the POM version was set to
> 2.0.1-SNAPSHOT even though I told it to set it to 2.1.0-SNAPSHOT.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
