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

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

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

   **[Michael 
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)**
 commented
   
   Please refer to 
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
 if you're wondering why this issue was closed out.
   




> Backslashes in Perforce clientspec name should be replaced
> ----------------------------------------------------------
>
>                 Key: SCM-416
>                 URL: https://issues.apache.org/jira/browse/SCM-416
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-provider-perforce
>    Affects Versions: 1.1
>         Environment: Linux (bash shell)
>            Reporter: Peter Janes
>            Priority: Major
>         Attachments: no-backslashes.patch
>
>
> The patch in SCM-370 doesn't actually fix the problem it claims to, namely 
> the presence of backslashes in clientspec names.
> The attached patch replaces the backslashes (and other special characters 
> already present) with "-", which also works around the related bugs 
> PLXUTILS-44 and CONTINUUM-1402.



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

Reply via email to