maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Venisse (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (SCM-281) Perforce problem: incorrect client spec is used
Date Tue, 13 Mar 2007 13:28:43 GMT

     [ http://jira.codehaus.org/browse/SCM-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Emmanuel Venisse updated SCM-281:
---------------------------------

    Fix Version/s: future

> 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
>             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 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

        

Mime
View raw message