[
http://jira.codehaus.org/browse/SCM-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88647
]
Anton Katernoga commented on SCM-281:
-------------------------------------
The purpose of SCM-165 isn't very clear to me, but from the comments I see it
was necessary for several commands to run with same persistent client spec. Why
do you save this specname in property although you can simply re-generate it
from repo and workDir each time and it will be the same name?
> Perforce problem: incorrect client spec is used
> -----------------------------------------------
>
> Key: SCM-281
> URL: http://jira.codehaus.org/browse/SCM-281
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Affects Versions: 1.0-beta-4
> Reporter: Anton Katernoga
> Assigned To: Mike Perham
> Attachments: patch.p4.txt
>
>
> I have 2 projects set up which use the same perforce scm url. One is run each
> 5 mins, the other is a nightly tests build. I've noticed that the latter
> never gets run-the message is that the dir is up-to date. It appeared that
> after the first project is run, its client spec is set to system variable in
> PerforceCheckOutCommand (maven-scm perforce provider) class and afterwards
> the value of the var is used instead of a correct client spec. I didn't
> remove the property set, as it is a fix to SCM-165, but rather the place
> where prop is used. Now works fine.
> Patch is attached.
--
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
