Summary: | [reconcile] Temporary problems reported but no problem markers | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Dani Megert <daniel_megert> | ||||
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> | ||||
Status: | CLOSED WONTFIX | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | philippe_mulet | ||||
Version: | 3.3 | ||||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | stalebug | ||||||
Attachments: |
|
Description
Dani Megert
2007-06-28 06:24:00 EDT
Also, the message 'Project was not built...' is wrong as some files got error markers i.e. something obviously got built. The message should be changed to something like 'Project was not fully built....' or 'The project has an incomplete build path: ...'. Might be related to bug 194432, where we don't insert working copies at the right place on the classpath during NameLookup. Bug 194432 is now fixed. Dani can you reproduce with the latest I-build ? I'd claim that my steps are simple enough for you guys to execute them yourselves - after all that's the idea of providing a test case, isn't it? Anyway, I did it once again and all reported issues are still there. Sorry, the words "Sometime" and "While I cannot reproduce exactly" confused me into thinking that this bug was not easily reproducible. I'll try your steps. >I'll try your steps.
Thanks. Actually this should allow you to debug it via your dev workspace.
Running runtime workbench on a new workspace I see issue #5 but not issue #6. I'm going to try with the SDK on a new workspace. Still cannot reproduce with I20070821-0800. TaskRulerAction has 1 annotation for "The type org.eclipse.core.commands.common.EventManager cannot be resolved. It is indirectly referenced from required .class files", but no other annotation. Did you open the CU? The errors only appear as temporary problems. Should be visible via Overview ruler. Created attachment 76899 [details]
Screenshot of editor opened on TaskRulerAction.java
Did I miss something ?
[Dani slaps his head on the desk] repeat many times ;-)
>6. open TaskRulerAction
Should read: open TemplatePreferencePage
When a missing .class file is detected, the Java builder assumes that there is a classpath problem (which is the case here) and removes all other problems (so that the user can concentrate on first fixing the classpath). We should also remove all other problems during reconcile. The Java builder code that removes the markers is in AbstractImageBuilder#storProblemsFor(...). Look for // handle missing classfile situation 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. |