[
https://issues.apache.org/jira/browse/MRELEASE-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15773096#comment-15773096
]
Luc Chapon commented on MRELEASE-951:
-------------------------------------
it works with --batch-mode if I put the developmentVersion in the properties
section of the main pom.xml
<properties>
<developmentVersion>9.0.40-SNAPSHOT</developmentVersion>
<autoVersionSubmodules>true</autoVersionSubmodules>
…/…
So, developmentVersion is taken into account either interactively, or in batch
mode if specified as a pom property, but not in batch mode and specified on the
command line by -D.
> 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)
