[ 
https://issues.apache.org/jira/browse/SCM-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960651#comment-17960651
 ] 

ASF GitHub Bot commented on SCM-215:
------------------------------------

jira-importer commented on issue #443:
URL: https://github.com/apache/maven-scm/issues/443#issuecomment-2964594863

   **[Emmanuel 
Venisse](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=evenisse)**
 commented
   
   you can put them in 
maven-scm-providers/maven-scm-providers-cvs/maven-scm-provider-cvs-commons/src/main/test/org/apache/maven/scm/provider/cvslib/AbstractCvsScmProviderTest.java
   




> Add ability to sanitise tag names
> ---------------------------------
>
>                 Key: SCM-215
>                 URL: https://issues.apache.org/jira/browse/SCM-215
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: New Feature
>          Components: maven-scm-api
>    Affects Versions: 1.0-beta-3
>            Reporter: Richard van der Hoff
>            Assignee: Emmanuel Venisse
>            Priority: Major
>             Fix For: 1.0-beta-4
>
>         Attachments: maven-scm-tag-sanitation-tests.pach, 
> maven-scm-tag-sanitation.patch
>
>
> In order to fix MRELEASE-110, the scm provider needs to provide a means of 
> turning a potential tag into a valid one.
> This patch adds a method to the provider API to allow this; it also provides 
> a suitable implementation for the cvs provider.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to