Community
Participate
Working Groups
Build Identifier: 20100917-0705 Helios Service Release 1 see also Bug 257347, Bug 106806, Bug 255931, Bug 239589 Reproducible: Always
Created attachment 185837 [details] ObjectCannotBeResolved.png ... and the additional errors visible top left of class-file editor
Created attachment 185838 [details] workSpaceSettings.png other projects depending on the same global profile compile like a charm
Created attachment 185839 [details] classpathProblems.png apparently, this was the reason
Suggestions: 1) Add a quick-fix that suggests to look at the .classpath 2) if the .classpath is the reason, don't just add a yellow warning, but a) make a red warning b) add a mouse-over that says more about the problem
(In reply to comment #4) > Suggestions: > 1) Add a quick-fix that suggests to look at the .classpath > 2) if the .classpath is the reason, don't just add a yellow warning, but > a) make a red warning > b) add a mouse-over that says more about the problem What's the problem with the .classpath file? Could you attach the classpath file here?
don't have the exact file anymore, but it was kind of empty - something like <?xml version="1.0" encoding="UTF-8"?> <classpath> <classpathentry kind="output" path="trunk/junit/classes"/> </classpath>
Jay, please investigate.
Nothing particularly wrong with the given .classpath file format that could have caused an error. When there is a format error with the .classpath file, a build path error is displayed in the problems view. Do you remember seeing it? Also, if you can share the log file when the error occurred, it would help.
Created attachment 186255 [details] Log file Thanks for the log file, Ralf. I have attached the relevant portion alone here. I am able to reproduce the exception trace when I corrupt the .classpath manually and after a refresh open the build path properties dialog. However, invariably the problems marker gets updated with the appropriate error message. I guess there is something else. Perhaps the refresh wasn't successful? Also I noticed some NPE (bug #326434), which have been fixed in 3.6 maintenance branch. So, I recommend you try a newer build.
(In reply to comment #9) > Also I noticed some NPE (bug #326434), which have been fixed in 3.6 maintenance > branch. So, I recommend you try a newer build. Did you get a chance to try this?
(In reply to comment #10) > Did you get a chance to try this? Ralf, any update on this?
Marking as 'RESOLVED'. Please reopen if the bug occurs again.
Verified for 3.7M5 using build I20110124-1800