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

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

jira-importer opened a new issue, #570:
URL: https://github.com/apache/maven-scm/issues/570

   **[zak 
jacobson](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=zoosnack)**
 opened 
**[SCM-351](https://issues.apache.org/jira/browse/SCM-351?redirect=false)** and 
commented
   
   The default generated client spec name is calculated in 
generateDefaultClientspecName() as:
   
   username + "−" + hostname + "−MavenSCM−" + path;
   
   if path includes a space or tilde, the client spec is not created and the 
plugin fails to sync.
   
   Can:
   
   ```
   path = workDir.getCanonicalPath().replace( '/', '\\' )
   ```
   
   be replaced with:
   
   ```
   path = workDir.getCanonicalPath().replace( '/', '\\' ).replaceAll("[ ~]", 
"-")
   ```
   
   
   
   ---
   
   **Affects:** 1.0
   
   **Issue Links:**
   - [SCM-370](https://issues.apache.org/jira/browse/SCM-370) generated client 
spec contains backslashes leading die problems on unix os
    (_**"duplicates"**_)
   
   1 votes, 1 watchers
   




> generated client spec name fails if there is a space or tilde in directory 
> name
> -------------------------------------------------------------------------------
>
>                 Key: SCM-351
>                 URL: https://issues.apache.org/jira/browse/SCM-351
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-provider-perforce
>    Affects Versions: 1.0
>            Reporter: zak jacobson
>            Assignee: Emmanuel Venisse
>            Priority: Major
>             Fix For: 1.1
>
>
> The default generated client spec name is calculated in 
> generateDefaultClientspecName() as:
>    username + "−" + hostname + "−MavenSCM−" + path;
> if path includes a space or tilde, the client spec is not created and the 
> plugin fails to sync.
> Can:
> {noformat}path = workDir.getCanonicalPath().replace( '/', '\\' ){noformat} 
> be replaced with:
> {noformat}path = workDir.getCanonicalPath().replace( '/', '\\' 
> ).replaceAll("[ ~]", "-"){noformat} 



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

Reply via email to