Community
Participate
Working Groups
Build ID: M20071023-1652 Steps To Reproduce: 1. Create a simple component to be used (like a customized JButton) and wrap it up in a jar as a custom library from within Eclipse. 2. Create a new Java project. 3. Create a new class in that project that will use an instance of the class in the custom library. 4. Create a lib folder within the project. 5. Import the custom jar library into the lib folder. 6. Add the imported jar to the class path. 7. Move the jar to the top of the Order and Export list. 8. Add the appropriate import statement to the top of the created class for the project. More information: The bug will appear as the library's name underlined in red so it won't compile. However, the custom library WILL appear in the Referenced Libraries section. I've also moved the custom library to the lib\ext folder of Java and, after removing it from that folder, tried adding it as an external jar to the class path. I've double- and triple- checked to make sure I typed everything correctly, but that's not the problem either. I currently have a workaround, but I have other projects that will require a common library that will make using the workaround very irritating very quickly.
> 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.
