Summary: | Can't Resolve Custom Library Jar Added to Classpath | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Worthy Sizemore <Worthy.Sizemore> | ||||
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> | ||||
Status: | VERIFIED WORKSFORME | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | darin.eclipse, jerome_lanneluc | ||||
Version: | 3.3.1 | ||||||
Target Milestone: | 3.5 M2 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Worthy Sizemore
2007-11-13 13:22:10 EST
> The bug will appear as the library's name underlined in red so it won't
compile.
I'm not sure to understand. The import statement is not supposed to reference the library name. Could you please give an example of the .java file you created?
Created attachment 82879 [details]
Example component for library
This is the java file of the class that I added as a component for the library that I packed into the jar file. However, when I tried to reference the library, it wouldn't resolve. I even attempted to have Eclipse offer a suggestion for an import after I created a new instance of the class when I had the library as part of the Referenced Libraries, but it failed to recognize it. Yet when I checked the jar in the Referenced Libraries listing, it even showed the compiled class.
After much struggling, managed to fix my own problem, but for future reference, the "Add Import" option doesn't work for custom libraries added to the build path. Please do not change resolution of a bug, a JDT/Core committer will do it. FYI: In this case, as nothing was fixed in our code, so the resolution is not correct. Resolution should then be WORKSFORME since we were not able to reproduce the problem. Verified for 3.5M2 using I20080914-2000. |