[
http://jira.codehaus.org/browse/SCM-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93205
]
Jan Edelbroek commented on SCM-142:
-----------------------------------
Does anybody have a solution yet for this problem?
I have the same problem too and it seems that starteam has sometimes troubles
with updating the status of the files.
Maybe this can be solved by using the update-status command (stcmd
update-status ...) first before doing the checkout from starteam. I think this
will solve most of the problems.
> 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
