[ http://jira.codehaus.org/browse/SCM-114?page=comments#action_53488 ]
mike perham commented on SCM-114: --------------------------------- The Perforce plugin will NOT obey P4CLIENT because it needs to support multiple clientspecs with Continuum. It will NOT obey P4PASSWD because it does not do any security. It assumes the p4 user is already logged in. When I tried to handle users and passwords, I ran into nothing but problems so I punted on that whole aspect. > 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
