Summary: | eclipse doesn't update metadata/index after JAR change | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | nbonatsakis |
Component: | Core | Assignee: | Jay Arthanareeswaran <jarthana> |
Status: | VERIFIED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | Olivier_Thomann |
Version: | 3.6 | ||
Target Milestone: | 3.7 M7 | ||
Hardware: | Macintosh | ||
OS: | Mac OS X - Carbon (unsup.) | ||
Whiteboard: |
Description
nbonatsakis
2010-08-27 10:18:46 EDT
I observe a similar behavior using last 3.7 I-build or 3.6.0 build but only if I do not save the change done in MyClass. When I save the file after having added the MyClass.foo() unresolved reference, then *all* errors vanish when I refresh the project and see in the Package Explorer the method foo added in the jar... Could you confirm that the behavior is correct when the editor on MyClass.java is not dirty (i.e. MyClass.java saved)? Even when the editor is dirty, the compiler errors go away after having waited a little while (using 3.7)... Just to be clear, in my scenario project.jar contains only a complied .class file for MyClass (MyClass.class) and is built completely outside of Eclipse. In other words, Project A is the only project in my Eclipse workspace, the only reference to projectb.jar is as a Build Path library dependency. Therefore, Eclipse has no idea of MyClass.java, and changes to it being saved or unsaved are completely irrelevant, it is assumed that it is compiled and added to projectb.jar. (In reply to comment #3) > Just to be clear, in my scenario project.jar contains only a complied .class > file for MyClass (MyClass.class) and is built completely outside of Eclipse. In > other words, Project A is the only project in my Eclipse workspace, the only > reference to projectb.jar is as a Build Path library dependency. Therefore, > Eclipse has no idea of MyClass.java, and changes to it being saved or unsaved > are completely irrelevant, it is assumed that it is compiled and added to > projectb.jar. I agree that comment 1 was definitely misleading :-( It should have read UseMyClass.java instead of MyClass.java! Definitely sorry about this mistake and the confusion... :-S I tried this with build ID I20110310-1119 and can't reproduce. I don't know if this has been fixed as part of another bug. Closing the bug - I would suggest you try with a newer build and if you still find this issue, please reopen. Thanks. Verified. If this happens again, please provide a test case that reproduces the issue. |