[ http://jira.codehaus.org/browse/SCM-114?page=comments#action_53425 ]
skylab commented on SCM-114: ---------------------------- It's true, you cannot use One client for all projects in Continuum. But I had to use a client-name in company style and found a solution to override it: You can use the System.property *maven.scm.perforce.clientspec.name* to override the clientname: e.g. *maven.scm.perforce.clientspec.name=my-company_uses_this_clientspec_name* There is also a flexible solution, when adding functionality in _maven-scm-providers_ to org/apache/maven/scm/provider/perforce/command/checkout/*PerforceCheckOutCommand* In method _createClientspec(String specname, String workDir, String repoPath)_: add the _repoPath_ parameter to _getClientspecName()_ method and build the name like suggested above! > Clientspec naming > ----------------- > > Key: SCM-114 > URL: http://jira.codehaus.org/browse/SCM-114 > Project: Maven SCM > Type: Improvement > Components: maven-scm-provider-perforce > Versions: 1.0-beta-3 > Reporter: mike perham > Fix For: 1.0-beta-3 > > > Several people have expressed more than a passing interest in how the > Perforce clientspec is named by Maven SCM. The name needs to be > autogenerated and unique for each Continuum project build. Currently I am > thinking something like: > ${project}-${user}-${hostname}-mavenscm > Emmannuel, does the SCM subsystem have access to the name of the project > being built? If not, I can just use the name of the last directory in the > SCM URL for the name of the project: //depot/projects/foobar would mean that > ${project} = foobar. > And just head off the inevitable question: you cannot set P4CLIENT for this > because Continuum may build several different projects and they each need a > unique clientspec. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
