[
http://jira.codehaus.org/browse/SCM-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated SCM-361:
-----------------------------
Fix Version/s: 1.1.1
> make cvs tag -F optional
> -------------------------
>
> Key: SCM-361
> URL: http://jira.codehaus.org/browse/SCM-361
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-cvs
> Affects Versions: 1.0
> Reporter: Benoit Decherf
> Fix For: 1.1.1
>
> Attachments: patch_useForceTag
>
>
> In our cvs server a tag cannot be moved. This is useful to ensure that there
> is only one version of a component with a same tag. Now, i wan't to integrate
> all our components to continuum and use it to create releases. The problem is
> that the scm try to tag the release using "cvs tag -F" and this fails.
> I check the code and see that it is hardcoded (in
> maven-scm-provider-cvs-commons/src/main/java/org/apache/maven/scm/provider/cvslib/command/tag/AbstractCvsTagCommand.java).
> Is it possible to make it optional ? Or what is the reason to enforce it ?
> I make a patch to add the option useForceTag. This works, but in case of a
> conflict with an existing flag, the cvs tag won't failed. (the tag is not
> set). Is this acceptable ?
> Or maybe I should check for Warning messages in the output and the command
> should fail if there are any warnings ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
