[
https://jira.codehaus.org/browse/SCM-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SCM-281.
------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
Assignee, if you think you can fix this bug anytime soon, please reopen and
proceed appropriately.
> Perforce problem: incorrect client spec is used
> -----------------------------------------------
>
> Key: SCM-281
> URL: https://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
> Assignee: Mike Perham
> Fix For: future
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
