[
https://jira.codehaus.org/browse/MRELEASE-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315535#comment-315535
]
Michael Wenig commented on MRELEASE-780:
----------------------------------------
We observed the following:
1. A release 0.1 is created (prepare/perfom) out of trunk. A Tag Release_0.1
gets created - ok
2. Work on trunk goes on
3. Someone decided to need a hotfix. So he creates a branch (release:branch)
out of the tag 0.1 - there the problems start. The release plugin does the
following:
# Change the Version to 0.1.1-SNAPSHOT and commit this into the tag!
# Create a branch based on the tag (with the changed version)
# Rollback the version to 0.1 in the tag and commit it!
So after it has finished we have a tag containing 0.1 as before and a branch
with version 0.1.1-SNAPSHOT
The problem lies in the fact that commits are done into the tag - a tag should
never be changed again. We have to ensure that this is followed and we tried to
put a hook into svn which prevents commits to tags. The hook works well but
prevents (at least) the creation of the branch - in this case correctly as
there are commits to the tag.
> Prevent Tag from additional commits
> ------------------------------------
>
> Key: MRELEASE-780
> URL: https://jira.codehaus.org/browse/MRELEASE-780
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
> Affects Versions: 2.3.2
> Reporter: E
>
> If you create an release from the branch there should be no commits on the
> tag-folder.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
