Bugzilla – Full Text Bug Listing
| Summary: | [Operations] Replace with latest from HEAD yields confusing error message if not refreshed again. | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Andreas Krüger <andreas.krueger> |
| Component: | CVS | Assignee: | platform-cvs-inbox <platform-cvs-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P5 | CC: | nboldt |
| Version: | 2.1 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | stalebug | ||
|
Description
Andreas Krüger
I would suggest being able to configure Eclipse to refresh automatically before a synch. That's a good suggestion! But it would not help to avoid the problem described in this particular bug. Certainly not if that configuration option happens to not be activated - and we want eclipse to work well in that case, too, don't we? All I've been asking for is a more specific error message. Post 3.0 Eclipse can now be configured to aitomatically keep in sync with the filesystem (General>Workspace>Refresh Automatically) Dear Michael, this bug reports "the wording of the error message is confusing". You say: "There is this configuration option - if you set it, the bug will not show." Does that solve the bug? Appearently, the Eclipse team thinks, that configuration option is not a good choice for everybody. ( I agree.) So it can be left unset. Obviously, the error message can still happen, if the configuration option is left unset. As far as I can tell, the wording is still confusing in that case. A bug is not fixed simply because it does not happen under some circumstances. Change the error message to something like "out of sync with file system" or so. Or even "possible reason: out of sync with file system". Point taken. we will try and improve the error message for 3.3. We do not plan on addressing this issue in 3.3. Patches will be accepted. *** Bug 157940 has been marked as a duplicate of this bug. *** (In reply to comment #4) > Eclipse can now be configured to aitomatically keep in sync with the filesystem > (General>Workspace>Refresh Automatically) > This may be true, but sometimes it's really slow to auto-update - and the confusing error message will appear again. This seems like a trivial thing to fix: isn't this just a matter of changing a properties file to use a diffferent, less obscure message? It's not a simple as that since the message being displayed is from a lower level component so we would need to catch the exception, detect that it is a local sync problem and add another message. Also interesting is the fact that there should be additional details indicating why the delete failed but they do not appear to be available in the screenshot that was provided. But, as you say, it should not be that difficult to fix. However, we have much more work than we have hands so I don't see us being able to find the time to fix this in 3.3. Patches are welcome if you want to take a crack at it. I understand the more work than hands situation - we're all in that boat. If you can point me to where the offending code is, I can maybe take a look at writing a patch for you. Where's the code that handles this stuff? org.eclipse.team.something, I presume? The best place to start would be the ReplaceOperation in the org.eclipse.team.cvs.ui plugin. 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. 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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie. |