[
https://issues.apache.org/jira/browse/MRELEASE-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673979#comment-16673979
]
Robert Scholte commented on MRELEASE-797:
-----------------------------------------
It has been quite some time since I had a look at that code.
Pure SemVer is now not possible, because the major version should be based on
compatibility. You can only do that after compilation, however Maven expects a
version from the start. I don't know about the status of the current module,
would be nice to see improvements on it when possible.
You should only have to specify the policy in the root-folder, from where the
maven-release-plugin is executed.
> support semantic versioning
> ---------------------------
>
> Key: MRELEASE-797
> URL: https://issues.apache.org/jira/browse/MRELEASE-797
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: update-versions
> Affects Versions: 2.3.2
> Environment: Maven 3.0.4
> Reporter: Matthew Daniel
> Assignee: Robert Scholte
> Priority: Minor
>
> When a project is using [semantic versioning|http://semver.org/], the
> maven-release-plugin will only increment the right-most version identifier
> (which corresponds to a "patch" release in semver terminology). It would be
> helpful if the maven-release-plugin understood the 3 normal release
> severities: major, minor and patch.
> Current behavior:
> # Given a {{pom.xml}} with version {{1.0.50-SNAPSHOT}}
> # When the user executes {{mvn release:update-versions -Dsemver=major}} (as a
> hypothetical syntax)
> # Then observe that {{pom.xml}} contains {{1.0.51-SNAPSHOT}}, not
> {{2.0.0-SNAPSHOT}} as a "major" release would dictate
> Expected behavior:
> # Given a pom version in {{X.Y.Z}} format
> # When one indicates the desired semantic version release level to
> maven-release-plugin
> # Then maven-release-plugin increments {{X.Y.Z}} according to the user's
> indicated release level
> It would be an error condition for the user to request a semantic version
> release level when the pom's version is not in {{X.Y.Z}} format (plus any
> miscellaneous trailing text as specified in rules 10, 11 or 12 of the semver
> specification).
> It is currently possible to work around this via manual construction of a
> {{release.properties}} file, but that requires a 2 step build process: run
> the script then run the Maven targets. Further, one would expect that all
> Maven projects that use semantic versioning would need to implement their own
> pre-release scripts, which is wasteful.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
