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

Posted to issues@maven.apache.org by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org> on 2007/03/13 14:28:36 UTC

[jira] Updated: (SCM-142) Starteam tree stale

     [ http://jira.codehaus.org/browse/SCM-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Venisse updated SCM-142:
---------------------------------

    Fix Version/s: future

> Starteam tree stale
> -------------------
>
>                 Key: SCM-142
>                 URL: http://jira.codehaus.org/browse/SCM-142
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-starteam
>         Environment: continuum-1.0.2
>            Reporter: Bob Herrmann
>             Fix For: future
>
>
> It only takes a few changes to starteam for the checked out filesystem to become hopelessly stale.  The only recovery option is to completely remove all files and startover.  Either the code checking out is not handing the timestamps correctly, or starteam command line has problems keeping a checked out tree in sync (this more likely - as we also see this problem with AntHill when using it's incremental builder.)   Possible fixes might be to detect 'unknown' status's and flush the checked out tree.  Or try using the 2005 bco command instead of stcmd.  

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