[SCM-370] generated client spec contains backslashes leading die problems on unix os

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0
• Fix Version/s: 1.1
• Component/s: maven-scm-provider-perforce
• Environment: UNIX
• Flags: Patch
• Assignee: Emmanuel Venisse
• Reporter: Sebastian Annies
• Created: 17/Mar/08 06:06
• Updated: 05/Apr/15 14:54
• Resolved: 14/May/08 16:18

Description

When a client is created it is named:

E.g. sannies-sojus-MavenSCM-\opt\continuum-1.1-beta-3-SNAPSHOT\apps\continuum\webapp\WEB-INF\working-directory\6

that is ok, but now comes the sync command and uses following commandline

/bin/bash c "p4 -d /opt/continuum-1.1-beta-3-SNAPSHOT/apps/continuum/webapp/WEB-INF/working-directory/1 -cbackground-sojus-MavenSCM\opt\continuum-1.1-beta-3-SNAPSHOT\apps\continuum\webapp\WEB-INF\working-directory\1 sync"

The Bash now removes the backslashes in the client name! The result is that the client is not existent and perforce returns with an error.
This is related to [PLXUTILS-44] and CONTINUUM-1402

I propose to use the underscore character instead of the backslash.

Issue Links

• is duplicated by: SCM-351 generated client spec name fails if there is a space or tilde in directory name