You are viewing a plain text version of this content. The canonical link for it is here.

Posted to scm-dev@maven.apache.org by "Jeff Jensen (JIRA)" <ji...@codehaus.org> on 2005/12/12 20:52:46 UTC

[jira] Commented: (SCM-110) Perforce should force sync

    [ http://jira.codehaus.org/browse/SCM-110?page=comments#action_53294 ] 

Jeff Jensen commented on SCM-110:
---------------------------------

Would you mind explaining further please?  mvn clean does not delete "source" files, only target files, so am wondering your premise.

The only time I can think of needing a force sync is when the use says to do a "full get latest", which in Perforce terms means to get it all again, even though I probably already have it.  For those in CVS land, this is cvs co vs cvs update.

When does your change make this happen?  The code change was in the checkout source file, so only on checkouts, or do other actions reuse this code?


> Perforce should force sync
> --------------------------
>
>          Key: SCM-110
>          URL: http://jira.codehaus.org/browse/SCM-110
>      Project: Maven SCM
>         Type: Bug

>   Components: maven-scm-provider-perforce
>     Reporter: mike perham
>  Attachments: force.txt
>
>
> It's not pretty but it's the only way to get sync to work when files could be deleted from the filesystem (e.g. mvn clean).

-- 
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