[
https://issues.apache.org/jira/browse/SCM-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961409#comment-17961409
]
ASF GitHub Bot commented on SCM-416:
------------------------------------
jira-importer opened a new issue, #632:
URL: https://github.com/apache/maven-scm/issues/632
**[Peter
Janes](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=peterj)**
opened
**[SCM-416](https://issues.apache.org/jira/browse/SCM-416?redirect=false)** and
commented
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.
---
**Affects:** 1.1
**Attachments:**
-
[no-backslashes.patch](https://issues.apache.org/jira/secure/attachment/12718551/no-backslashes.patch)
(_957 bytes_)
> 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)
