[
https://issues.apache.org/jira/browse/SCM-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964408#comment-17964408
]
Olivier Lamy commented on SCM-221:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#479|https://github.com/apache/maven-scm/issues/479].
> scm:update has no effect
> ------------------------
>
> Key: SCM-221
> URL: https://issues.apache.org/jira/browse/SCM-221
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Affects Versions: 1.0-beta-4
> 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
> Assignee: Mike Perham
> Priority: Critical
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
