Community
Participate
Working Groups
Once the user stores either the source attachment path of Javadoc location path for a referenced library, it doesn't get removed when the referencing JAR is removed from build path. Steps: 1. Create two JARs one referencing another via MANIFEST.MF (let's say lib1.jar references lib2.jar) 2. Add the referencing JAR to the build path of a Java project => The package explorer shows both the JAR files as referenced libraries. 3. Select lib2.jar and Alt + Enter => Java source attachment dialog appears. 4. Input some value and click 'OK' => Check that the project's .classpath gets an entry for lib2.jar with tag <referencedentry/> 5. Now from project's build path, remove lib1.jar => Both lib1.jar and lib2.jar disappear from the package explorer. 6. However, looking at the .classpath, the <referencedentry/> for lib2.jar is left behind. Opening bug against JDT/UI ,although I am not entirely sure if JDT/UI can handle this. If it's possible for UI to compute the new referenced entries list, then perhaps the following API can be used: IJavaProject.setRawClasspath(IClasspathEntry[], IClasspathEntry[], IPath, IProgressMonitor) Else, JDT/Core will have to look for such orphaned entries and remove them while saving the .classpath file.
Markus, please have a look.
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.
