Community
Participate
Working Groups
The CVS Team > Update command often quits on me due to a resource error. If I do a Refresh (F5) and try again it works fine. I would like the Update to do the refresh for me so it will just work. Here's a typical traceback from the Eclipse error log (3.2M3, WinXP). The files it is complaining about were created outside Eclipse. Error 2006-01-18 11:53:48.792 Could not create resource /olap/misc/mdxsii.html: Problem writing resource '/olap/misc/mdxsii.html'. Resource /olap/misc/mdxsii.html already exists. org.eclipse.team.internal.ccvs.core.CVSException[374]: org.eclipse.core.internal.resources.ResourceException: Resource /olap/misc/mdxsii.html already exists. at org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:299) at org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:272) at org.eclipse.core.internal.resources.File.create(File.java:109) at org.eclipse.core.internal.resources.File.create(File.java:179) at org.eclipse.team.internal.ccvs.core.resources.EclipseFile.setContents(EclipseFile.java:182) at org.eclipse.team.internal.ccvs.core.client.Session.receiveFile(Session.java:792) at org.eclipse.team.internal.ccvs.core.client.UpdatedHandler.receiveTargetFile(UpdatedHandler.java:119) at org.eclipse.team.internal.ccvs.core.client.UpdatedHandler.handle(UpdatedHandler.java:100) at org.eclipse.team.internal.ccvs.core.client.Request.executeRequest(Request.java:218) at org.eclipse.team.internal.ccvs.core.client.Command.doExecute(Command.java:404) at org.eclipse.team.internal.ccvs.core.client.Update.doExecute(Update.java:180) at org.eclipse.team.internal.ccvs.core.client.Command$1.run(Command.java:323) at org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer.run(EclipseSynchronizer.java:1450) at org.eclipse.team.internal.ccvs.core.resources.EclipseResource$2.run(EclipseResource.java:260) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1714) at org.eclipse.team.internal.ccvs.core.resources.EclipseResource.run(EclipseResource.java:257) at org.eclipse.team.internal.ccvs.core.client.Command.execute(Command.java:335) at org.eclipse.team.internal.ccvs.core.client.Command.execute(Command.java:785) at org.eclipse.team.internal.ccvs.ui.operations.UpdateOperation.executeCommand(UpdateOperation.java:77) at org.eclipse.team.internal.ccvs.ui.operations.SingleCommandOperation.execute(SingleCommandOperation.java:42) at org.eclipse.team.internal.ccvs.ui.operations.RepositoryProviderOperation.execute(RepositoryProviderOperation.java:227) at org.eclipse.team.internal.ccvs.ui.operations.SingleCommandOperation.execute(SingleCommandOperation.java:66) at org.eclipse.team.internal.ccvs.ui.operations.RepositoryProviderOperation.execute(RepositoryProviderOperation.java:206) at org.eclipse.team.internal.ccvs.ui.operations.RepositoryProviderOperation.execute(RepositoryProviderOperation.java:190) at org.eclipse.team.internal.ccvs.ui.operations.CVSOperation.run(CVSOperation.java:79) at org.eclipse.team.internal.ui.actions.JobRunnableContext.run(JobRunnableContext.java:146) at org.eclipse.team.internal.ui.actions.JobRunnableContext$ResourceJob.runInWorkspace(JobRunnableContext.java:72) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
There is an auto-refresh preference which will keep your workspace in-sync with the file system (General/Workspace>Refresh automatically). Is there a reason you don't want to enable auto-refresh (or did you just not know about it)? The reason I ask is that we would not want to refresh on update/sync by default since that adds overhead to every operation. This means we would need a preference. I'm not sure that there would be any benefit to having a preference to auto-refresh and another preference to refresh on update/sync. The one thing we could do is handle the out-of-sync better. Perhaps offer to refresh and re-run the operation (although this type of error recovery tends to be difficult to implement).
I don't use the refresh automatically option because it didn't work well for me, something to do with the way our network storage was set up IIRC.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
