[
https://jira.codehaus.org/browse/MRELEASE-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315690#comment-315690
]
Michael Wenig commented on MRELEASE-780:
----------------------------------------
Hi Darryl,
bq. Can everyone with an interest in this ticket declare their SCM provider
type ? svn ? git ? they work differently and the original code has an SVN bias.
We are using JavaSVN
bq. Also that if an SCM provider allows modification of a tag (as a feature of
that system) then if users of that SCM provider need to enforce a 'can not
change tag revision policy' it should always be enforced by the server. You
should treat this as a feature of the SCM provider you need to disable for your
use case. This is just stated to reinforce whose responsibility it is to
enforce such a policy. This has no effect on making the Maven release plugin
better i.e. while I may not fully understand the nature of what is being
explained (because I have yet to sit down and repeat the sequence and examine
the behaviour described first hand).
I aggree that the enforcement is a scm-server-side task. Currently this is just
not possible as the release plugin is not able to work anymore.
bq. That being SVN needed it. However in light of this explanation what would
the repercussions of simply switching around the order of the 2 states:
scm-commit-branch AND scm-branch ? Without me working on adding a new state
'scm-branch-prepare'
Is it possible to do the switch by configuration (without changing the
release-plugin)? If yes I would try it out at our site.
Regards Michael
> 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
