Maven SCM

Perforce problem: incorrect client spec is used

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.0-beta-4
  • Fix Version/s: future
  • Component/s: maven-scm-provider-perforce
  • Labels:
    None
  • Complexity:
    Intermediate
  • Patch Submitted:
    Yes
  • Number of attachments :
    1

Description

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.

  1. Text File
    patch.p4.txt
    23/Feb/07 10:05 AM
    0.6 kB
    Anton Katernoga

Activity

Ascending order - Click to sort in descending order
Mike Perham made changes -
Field Original Value New Value
Component/s maven-scm-provider-perforce [ 11194 ]
Project Continuum [ 10540 ] Maven SCM [ 10527 ]
Affects Version/s 1.0.3 [ 12330 ]
Component/s SCM [ 12226 ]
Key CONTINUUM-1183 SCM-281
Affects Version/s 1.0-beta-4 [ 12574 ]
Mike Perham made changes -
Assignee Mike Perham [ mperham ]
Emmanuel Venisse made changes -
Fix Version/s future [ 12423 ]
Brett Porter made changes -
Patch Submitted [Yes]

People

  • Assignee:
    Mike Perham
    Reporter:
    Anton Katernoga
Vote (2)
Watch (4)

Dates

  • Created:
    Updated: