[
https://issues.apache.org/jira/browse/SCM-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964530#comment-17964530
]
Olivier Lamy commented on SCM-361:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#572|https://github.com/apache/maven-scm/issues/572].
> make cvs tag -F optional
> -------------------------
>
> Key: SCM-361
> URL: https://issues.apache.org/jira/browse/SCM-361
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-cvs
> Affects Versions: 1.0
> Reporter: Benoit Decherf
> Assignee: Siveton Vincent
> Priority: Major
> Fix For: 1.2
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
