Community
Participate
Working Groups
Build Identifier: 20100617-1415 There is an (old) jar in my Java project as "Referenced Library". I wan't to remove it but the context menu "Delete" function is disabled (ghosted) - even though the project's "Java Build Path" does not have this JAR anymore! Reproducible: Always Steps to Reproduce: 1. Remove JAR from Project's "Java Build Path" 2. Try to delete the JAR from the Package Explorer project "Referenced Libraries" node 3.
Does refreshing the project or closing and opening the project help?
Jay, a similar bahavior is seen in bug 310764. Referenced libraries continue to show deleted jars. It might help to check if this is the bahaviour in all cases or only for bad JAR files.
This should be investigated for 3.6.1.
I guess it has something to do with the new feature tha suddenly the JARE as some comment "from class-path of xyz.jar"). I found out, that the whole project doesn't compile anymore when a referenced library has a manifest with a class-path setting that has an entry of a JAR that doesn't exist anymore! I had to change the manifest file (remove the old JAR in the Class-Path), make a JAR of the referenced lib and copy it into my project. With the former Eclipse version, the manifest Class-Path didn't matter for Eclipse.
Investigating.
(In reply to comment #4) > I guess it has something to do with the new feature tha suddenly the JARE as > some comment "from class-path of xyz.jar"). I found out, that the whole > project doesn't compile anymore when a referenced library has a manifest with a > class-path setting that has an entry of a JAR that doesn't exist anymore! I had > to change the manifest file (remove the old JAR in the Class-Path), make a JAR > of the referenced lib and copy it into my project. > > With the former Eclipse version, the manifest Class-Path didn't matter for > Eclipse. If you are not setting source attachment path or avadoc location path for any of the referenced libraries, the behavior should be almost similar to 3.5. I think it would help if you can attach the zipped project to the bugzilla.
Alright, I somewhat misunderstood the problem reported. This is the behavior I am seeing with eclipse 3.6 (build I20100608-0911): When I add a JAR that references a non-existent JAR via it's MANIFEST to a project's build path, the referenced JAR is not shown in the referenced libraries. However, when I put the referenced JAR in the folder and close/reopen the project, it is included in the package explorer. I do not see any errors on missing JAR or resultant compilation errors. Markus, can you please confirm if this behavior is correct?
I gave it another try with 3.8 M6 but don't see any compilation error whatsoever. Runtime error, yes. This is a very old bug and haven't heard from since long. Should it occur again, please reopen.
Using Build id: I20120429-2000, I could see the behavior described in comment# 0 only for external jars. For jars that reside inside the work space, I could see the delete menu item and also use it to delete the entry concerned. The delete menu items does appear grayed out for external jars, but I think that is the right behavior. Verified for 3.8 M7 using I20120429-2000
