Basically what I described in my email this morning. It was easier than
I thought because Perforce does not distinguish between creating a new
clientspec and updating an old one. No need to query to see if it
already exists, in other words... I allow a system property
"maven.scm.perforce.client.name" to override the spec name otherwise I
just concat System.getProperty("user.name"), hostname and "maven"
together. Unfortunately I don't know of any way to get access to the
values in settings.xml and I don't want to add to the SCM URL so a
system property is the best I can support, AFAIK.
mike
-----Original Message-----
From: Jeff Jensen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 29, 2005 11:35 AM
To: scm-dev@maven.apache.org
Subject: Re: [jira] Created: (SCM-89) Add checkout to working directory
support to Perforce
Fantastic Mike! Sans digging through all the code, what did you end up
implementing??
Quoting "mike perham (JIRA)" <[EMAIL PROTECTED]>:
> Add checkout to working directory support to Perforce
> -----------------------------------------------------
>
> Key: SCM-89
> URL: http://jira.codehaus.org/browse/SCM-89
> Project: Maven SCM
> Type: Bug
> Components: maven-scm-provider-perforce
> Versions: 1.0-beta-2
> Reporter: mike perham
> Fix For: 1.0-beta-2
>
>
> Attached is a patch will adds the ability to check out code to an
> arbitrary directory as requested by Emmanuel and discussed by myself
> and Jeff Jensen last night on the scm-dev mailing list.
>
> --
> 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
>
>
