[ http://jira.codehaus.org/browse/SCM-221?page=all ]
Mike Perham closed SCM-221.
---------------------------
Resolution: Won't Fix
Fix Version/s: 1.0
There's no clear issue here so I'm closing this unless you have more specific
feedback. The property is "maven.scm.perforce.clientspec.name".
> scm:update has no effect
> ------------------------
>
> Key: SCM-221
> URL: http://jira.codehaus.org/browse/SCM-221
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Affects Versions: 1.0
> Environment:
> http://svn.apache.org/maven-snapshot-repository/org/apache/maven/scm/maven-scm-provider-perforce/1.0-SNAPSHOT/maven-scm-provider-perforce-1.0-20060616.160825-6.jar
>
> Reporter: Yuri Schimke
> Assigned To: Mike Perham
> Priority: Critical
> Fix For: 1.0
>
>
> We are trying to use scm:update in a cruisecontrol build to update the
> project before building. However it doesn't seem to actually write any
> changes to disk.
> The command completes successfully, but the files are not synced to head.
> The directory for the update is a working perforce directory. i.e. after the
> command below fails to update the files, "p4 sync" works immediately.
> [INFO] [scm:update]
>
> [INFO] Checkout working directory: C:\PerforceViews\dms_1.2_dev\dms
>
> [INFO] Executing: p4 client -i
>
> [INFO] Executing: p4 client -d
> nbk7xsp-B001279A7BC2E-MavenSCM-C:\PerforceViews\dms_1.2_dev\dms
>
>
> Is the generated clientspec just using for determining changesets? There is
> a valid clientspec already associated with the current project directory.
--
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
