Community
Participate
Working Groups
Created attachment 223132 [details] Adding the jar to the user library I added a user library and added a jar to that library. When I come back to the User Libraries screen, I get a "missing" and red X next to the added jar. In the past, I have successfully added dozens of jars to a user library without incident. This is not an intermittent problem; it happens every time I add a jar to a user library. I have looked at the jars in 7zip and the jar looks reasonable. I have tried this both from the Window -> Preferences -> Java -> build path -> User libraries route and another route (by clicking on a project -> build path -> Configure build path). I have tried changing the JDK based on http://stackoverflow.com/questions/4717932/add-jars-to-user-libraries-in-eclipse-helios-mac-osx. Went from JDK 1.6.0_25 to 1.7.0 and back again. I have also tried re-starting Eclipse with a -clean argument.
This works for me. Please try with 3.8.1 or later. If you can reproduce, then post the full OS path to the JAR you're trying to add. Maybe the problem is a special character in that path.
I have found out more what causes the problem and have found a workaround. The problem is caused when I choose Preferences -> Java -> Build Path -> User Libraries | Add JARS... and add a new jar file. What happens is that although the user library is given an absolute path (C:\Documents and Settings\a23456\box_corefx\1box-corefx\box-build\target\deployment\weblogic\APP-INF\lib\antlr-2.7.6.jar) it only stores a relative path (\1box-corefx\box-build\target\deployment\weblogic\APP-INF\lib\antlr-2.7.6.jar). This relative path is what makes it say "missing." The workaround is to export a good user library and massage a directory of the jars so that it has entries like: <archive path="C:/Documents and Settings/a23456/box_corefx/1box-corefx/box-build/target/deployment/weblogic/APP-INF/lib/antlr-2.7.6.jar"/> Then import the new user library.
Is your workspace at "C:/Documents and Settings/a23456/box_corefx" and "1box-corefx" is a project in your workspace? If yes, then the relative path is expected. For JARs from the workspace, we only save a relative path, so that the reference doesn't break when the workspace is renamed or moved. I still can't reproduce any problem. The relative path is correctly resolved for me.
Closing. Please reopen if you have more information.
