Summary: | [render] External chained jars are not correctly displayed | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Jerome Lanneluc <jerome_lanneluc> | ||||||
Component: | UI | Assignee: | Dani Megert <daniel_megert> | ||||||
Status: | RESOLVED FIXED | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | P3 | CC: | daniel_megert, frederic_fusier | ||||||
Version: | 3.4 | ||||||||
Target Milestone: | 3.5 M4 | ||||||||
Hardware: | PC | ||||||||
OS: | Windows XP | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Created attachment 116420 [details]
Libraries to reproduce the problem
To reproduce:
1. Expand the attached zip in D:\temp
2. Create a new Java project
3. Add D:\temp\lib1.jar to its buildpath
Observe: lib1.jar appears twice.
Instead, it should show lib2.jar and lib1.jar
I verified that the resolved classpath returned by JDT/Core is correct.
Fixed in HEAD. Available in next N-build for 3.5 M4. |
Created attachment 116419 [details] Screenshot of Package Explorer I20081029-0100 If an external jar "lib1.jar" references another external jar "lib2.jar" though the Class-Path: of its manifest, then the package explorer shows "lib1.jar" twice. This works fine if "lib1.jar" and "lib2.jar" are internal to the project.