[
https://issues.apache.org/jira/browse/MRELEASE-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-477.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Add a commitBeforeTag option for release:prepare to allow skipping
> scm-commit-release
> -------------------------------------------------------------------------------------
>
> Key: MRELEASE-477
> URL: https://issues.apache.org/jira/browse/MRELEASE-477
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: prepare
> Reporter: Mike Dillon
>
> As detailed in this thread, there can be reproducibility problems with
> committing to the source branch (e.g. trunk) before tagging:
> http://www.nabble.com/Limitation-of-the-release-plugin--to20822478.html
> In the now default case where remoteTagging is true, the commit to the source
> branch is necessary to get the source into the right state before doing the
> remote copy. However, when remoteTagging is false, the extra commit means
> that between the user's initial checkout and the automatic commit to the
> source branch, other changes could have been committed which will mean that
> the new tag will not have been created from a single, consistent revision of
> the source branch.
> My proposed fix for this is to add a commitBeforeTag option that would cause
> scm-commit-release to be skipped during release:prepare. It would be an error
> to have commitBeforeTag=false when remoteTagging=true since the commit before
> tag must be done in the remote tagging scenario.
> I can provide a patch if this approach is acceptable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
