Red Hat Bugzilla – Bug 219760
Eclipse doesn't handle simultaneous svn access from commandline
Last modified: 2008-05-06 13:11:31 EDT
Description of problem: When accessing files from the commandline (such as quick ant run / test / change / etc), and checking them back into subversion (or even altering svn properties) causes eclipse to have problems. Version-Release number of selected component (if applicable): rpm -qa | grep eclipse eclipse-rcp-3.2.1-23.fc6 eclipse-cdt-3.1.1-1.fc6 eclipse-gef-3.2.1-2.fc6 eclipse-bugzilla-0.2.4-3.fc6 eclipse-subclipse-1.1.8-2.fc6 eclipse-ecj-3.2.1-23.fc6 eclipse-changelog-2.3.3-2.fc6 eclipse-platform-sdk-3.2.1-23.fc6 eclipse-platform-3.2.1-23.fc6 eclipse-rcp-sdk-3.2.1-23.fc6 eclipse-jdt-3.2.1-23.fc6 eclipse-pde-3.2.1-23.fc6 eclipse-gef-sdk-3.2.1-2.fc6 eclipse-pde-runtime-3.2.1-23.fc6 eclipse-subclipse-book-1.1.8-2.fc6 eclipse-gef-examples-3.2.1-2.fc6 How reproducible: Frequently. Depending on how it's done as to the results. It's annoying now, and the solution is to ensure it's all checked in from the command line ('coz eclipse doesn't think it's a repo anymore...), wipe the project and re-check out the project. Steps to Reproduce: 1. Use SVN Repo exploring to checkout a project. 2. Maybe modify a file using eclipse (unsure) 3. Bring up a console in Eclipse's workspace and modify a file, or file's properties (svn:keywords for example), and (optionally) check the file in. Actual results: A refresh (F5) or team->update of the file / directory / project causes Eclipse to come up with something like: "update -r HEAD /home/austin.arrowsmith/workspace/<project>/build svn: Working copy 'build' is missing or not locked" Or my favourite: "svn: '/home/austin.arrowsmith/workspace/<project>/build' is not under version control" Expected results: For it to update it self to what is now in the repo (or file system), like the _real_ version of Eclipse used to under FC4... Additional info: I'll provide some screen shots of some messages that it pops up. Unsure how useful they'll be, but I'll provide them because they did pop up. Perhaps some more information should be in the dialogs when these errors occur?
Created attachment 143740 [details] Screen shot of the error that Eclipse encounters
Created attachment 143741 [details] The other error that was present in the same dialog Not too brilliant in it's helpfulness for tracking down the cause, but at least you know the problem exists.
Is this perhaps a Subclipse bug? Fedora Extras -> eclipse-subclipse CCing Robert to get his opinion
I think this is either an upstream issue or a problem with subclipse. Moving to Fedora Extras -> eclipse-subclipse to get Roberts opinion.
I have been unable to repeat those errors with the current eclipse-subclipse release (1.1.9) Does the new release solves the bug?
Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.