[ http://jira.codehaus.org/browse/SCM-221?page=comments#action_70087 ] Yuri Schimke commented on SCM-221: ----------------------------------
We are trying to use the perforce support for three things. 1) scm:update in cruisecontrol - must use existing clientspec 2) maven-changelog-plugin - can use either existing or generated clientspec 3) release - must use generated clienspec 1&2 are run in cruise control, 2&3 are run locally. I guess we should set it just for the cruisecontrol box. Is that the idea? > 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 > > 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
