Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 437359

Summary: [package explorer] Incorrect selection in Package Explorer after adding an external library which is already referenced in another project
Product: [Eclipse Project] JDT Reporter: Wojciech Sudol <sudol.wojciech>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: stephan.herrmann, sudol.wojciech
Version: 3.8.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug

Description Wojciech Sudol CLA 2014-06-13 07:01:30 EDT 
Scenario:
1. Create two java projects - Project1 and Project2
2. Add an external library to the Project1 by opening a context menu on the Project1 in the Package Explorer and choosing "Build Path" > "Add External Archives..."
3. Add the same external library to the Project2 in the same way.

Expected behaviour:
In the Package Explorer the Project2 is expanded and its newly added external library is selected.

Current behaviour:
In the Package Explorer the Project2 is collapsed. Instead the external library under Project1 is selected.

Reproduced in Eclipse 3.7.2 and 4.4 RC4.
Comment 1 Noopur Gupta CLA 2014-06-16 02:58:30 EDT 
Reproducible in Eclipse 3.8.1 also.
Comment 2 Eclipse Genie CLA 2020-03-11 19:22:35 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Stephan Herrmann CLA 2020-03-12 06:37:52 EDT 
I don't even think this can be avoided given the current design of the Java model: jar files are shared between projects, so there really is only one JarPackageFragmentRoot representing the library for all projects that reference the it.