[
https://issues.apache.org/jira/browse/MRELEASE-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712387#comment-17712387
]
Karl Heinz Marbaise commented on MRELEASE-1119:
-----------------------------------------------
No. The property file contained the same versions as your pom file already
contained (next release versions implied by the existing SNAPSHOT versions)
which looks like it's working but it does not working that way. Just set your
version in your pom file to lets say {{3.2.0-SNAPSHOT}} commit that and then
define the content of your {{release.properties}} file with the following:
{code}
tag=release-3.3.0
releaseVersion=3.3.0
developmentVersion=3.4.0-SNAPSHOT {code}
{code}
and just try to run: {{mvn -B release:prepare}} and look in the pom and the
created tag etc... it will tag: 3.2.0 and your pom (last commit will be 3.2.0)
etc. so not workgin at all...as documented...
If you in contradiction fill the {{release.properties}} file with correct
key/value pairs like this:
{code}
scm.tag=release-3.3.0
project.dev.io.rhpatrick.test\:mrp-test=3.4.0-SNAPSHOT
project.rel.io.rhpatrick.test\:mrp-test=3.3.0
{code}
and run {{mvn -B release:prepare}} you will see the difference...
> release plugin ignores developmentVersion
> -----------------------------------------
>
> Key: MRELEASE-1119
> URL: https://issues.apache.org/jira/browse/MRELEASE-1119
> Project: Maven Release Plugin
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Robert Patrick
> Assignee: Karl Heinz Marbaise
> Priority: Major
>
> I just ran a release process using the 3.0.0 version of the
> maven-release-plugin with a release.properties file like this:
> {{tag=release-3.0.4}}
> {{releaseVersion=3.0.4}}
> {{developmentVersion=3.1.0-SNAPSHOT}}
> After running {{mvn -B release:prepare release:perform}}, the pom.xml version
> is 3.0.5-SNAPSHOT.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
