[
http://jira.codehaus.org/browse/SCM-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92132
]
Emmanuel Venisse commented on SCM-292:
--------------------------------------
Possible solution without modification in continuum:
instead of system property, we can store the clientspec in
${user.home}/.scm/perforce.xml (other providers use a xml file to configure the
provider too)
In this file we store a mapping between the scmurl and the clientspec
{noformat}
<settings>
<clientSpecMappings>
<clientSpecMapping>
<scmUrl>scm:perforce:[EMAIL
PROTECTED]:port:path_to_repository1</scmUrl>
<clientSpecName>username-host-MavenSCM-path-to-repo1</clientSpecName>
</clientSpecMapping>
<clientSpecMapping>
<scmUrl>scm:perforce:[EMAIL
PROTECTED]:port:path_to_repository2</scmUrl>
<clientSpecName>username-host-MavenSCM-path-to-repo2</clientSpecName>
</clientSpecMapping>
</clientSpecMappings>
</settings>
{noformat}
and in PerforceScmProvider.getClientspecName(...) we return the clientSpecName
from the xml file. If if doesn't exist, we generate a default name and we store
it in the xml file.
WDYT?
> Replace DEFAULT_CLIENTSPEC_PROPERTY system property by a map to store in
> memory clientspec names
> ------------------------------------------------------------------------------------------------
>
> Key: SCM-292
> URL: http://jira.codehaus.org/browse/SCM-292
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Affects Versions: 1.0-beta-4
> Reporter: Emmanuel Venisse
> Assigned To: Patrick Schneider
> Priority: Critical
> Fix For: 1.0
>
>
> With a Map instead of a system property, we'll can support more that one
> clientspec in the jvm. It's necessary for Continuum because it access to more
> than one project in Perforce.
--
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
