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

Michael Osipov closed SCM-142.
------------------------------

    Resolution: Won't Fix

Please refer to 
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
 if you're wondering why this issue was closed out.

> Starteam tree stale
> -------------------
>
>                 Key: SCM-142
>                 URL: https://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 was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to