[
https://issues.apache.org/jira/browse/MRELEASE-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712129#comment-17712129
]
Karl Heinz Marbaise edited comment on MRELEASE-1119 at 4/14/23 12:08 AM:
-------------------------------------------------------------------------
Ah great [~rhpatrick00] thanks for those detailed information that helps a lot
to understand your problem. The issue was that your {{release.properties}} did
not contained the correct information... if you create a {{release.properties}}
file like this:
{code}
scm.tag=release-3.0.4
project.dev.org.apache.maven.plugin.release.its\:mrelease-1119=3.1.0-SNAPSHOT
project.rel.org.apache.maven.plugin.release.its\:mrelease-1119=3.0.4
{code}
where the part: {{org.apache.maven.plugin.release.its}} represents the groupId
of your project and the {{mrelease-1119}} is the artifactId of your project.
The prefixing part {{project.dev.}} is the development version and the
{{project.rel.}} is the project release version. By using that it creates the
correct results.
By using the wrong {{release.properties}} the integration tests exactly shows
the described (from your point of view) wrong behaviour. Using the correct
content it behaves exactly as it should...
So the {{release.properties}} file for your test project (mrpm-test) should
look like this:(assumed your starting version in your project is
{{3.0.4-SNAPSHOT}}):
{code}
scm.tag=release-3.0.4
project.dev.io.rhpatrick.test\:mrp-test=3.1.0-SNAPSHOT
project.rel.io.rhpatrick.test\:mrp-test=3.0.4
{code}
This is also documented here:
https://maven.apache.org/maven-release/maven-release-plugin/usage/non-interactive-release.html#using-a-properties-file
It might be easier to just define the new development version via command like
this: {{mvn -B -DdevelopmentVersion=3.1.0-SNAPSHOT release:prepare
release:perform}} and the rest will be taken from the {{pom.xml}} and the
increment will be done by default on the patch level...
was (Author: khmarbaise):
Ah great [~rhpatrick00] thanks for those detailed information that helps a lot
to understand your problem. The issue was that your {{release.properties}} did
not contained the correct information... if you create a {{release.properties}}
file like this:
{code:text}
scm.tag=release-3.0.4
project.dev.org.apache.maven.plugin.release.its\:mrelease-1119=3.1.0-SNAPSHOT
project.rel.org.apache.maven.plugin.release.its\:mrelease-1119=3.0.4
{code}
where the part: {{org.apache.maven.plugin.release.its}} represents the groupId
of your project and the {{mrelease-1119}} is the artifactId of your project.
The prefixing part {{project.dev.}} is the development version and the
{{project.rel.}} is the project release version. By using that it creates the
correct results.
By using the wrong {{release.properties}} the integration tests exactly shows
the described (from your point of view) wrong behaviour. Using the correct
content it behaves exactly as it should...
So the {{release.properties}} file for your test project (mrpm-test) should
look like this:(assumed your starting version in your project is
{{3.0.4-SNAPSHOT}}):
{code}
scm.tag=release-3.0.4
project.dev.io.rhpatrick.test\:mrp-test=3.1.0-SNAPSHOT
project.rel.io.rhpatrick.test\:mrp-test=3.0.4
{code}
This is also documented here:
https://maven.apache.org/maven-release/maven-release-plugin/usage/non-interactive-release.html#using-a-properties-file
It might be easier to just define the new development version via command like
this: {{mvn -B -DdevelopmentVersion=3.1.0-SNAPSHOT release:prepare
release:perform}} and the rest will be taken from the {{pom.xml}} and the
increment will be done by default on the patch level...
> 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)
