maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Perham (JIRA)" <>
Subject [jira] Commented: (SCM-281) Perforce problem: incorrect client spec is used
Date Mon, 26 Feb 2007 15:46:15 GMT


Mike Perham commented on SCM-281:

Does Continuum have a way to set the environment variables for a build before the build is
executed?  If yes, you should be setting the clientspec system property to the proper value
for each build beforehand.  That patch is unacceptable because it removes the ability to specify
the clientspec as a system property.

> Perforce problem: incorrect client spec is used
> -----------------------------------------------
>                 Key: SCM-281
>                 URL:
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-perforce
>    Affects Versions: 1.0-beta-4
>            Reporter: Anton Katernoga
>         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:
For more information on JIRA, see:


View raw message