Bugzilla – Full Text Bug Listing
| Summary: | Export to runnable jar creates non-functional jar when library jars have a soft link in their path | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Michael Woodhams <michael.woodhams> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | minor | ||
| Priority: | P3 | CC: | jarthana |
| Version: | 3.8.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | stalebug | ||
I believe this feature is part of UI. Moving to JDT/UI. 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. |
I had a linux box where my userid was "woodhams". I created a Java project and used "Add external jar" option in the project java build path. I moved to a new Linux box where I was user "mdw2". I copied my home directory (including Eclipse workspace) from the old machine to the new one. As there were various places where paths to /home/woodhams/... were recorded, rather than try to hunt them all down, I made /home/woodhams a soft link ("ln -s") to /home/mdw2. The result was that the java project with pointers to external jars in /home/woodhams/... worked fine in Eclipse (compiled and ran OK) but when I ran "file->export->runnable jar file" it would produce a jar file without external libraries which had been added as external jars. (This is independent of the 'extract required libraries'/'package required libraries'/'copy required libraries into subfolder' option - all these still failed to produce something runnable.) I get a message that the Jar export finished with warnings: 'Fat jar export: could not find class-path entry for 'home/mdw2/workspace/[...]/library.jar'". Running the jar generates a java.lang.NoClassDefFoundError error. Workaround: remove the jars from the Java build path and add them again with the correct path. Desired outcome: Export to jar should work, even if the external jars have a soft link in their path. OS: Ubuntu 14.04 Java version: 1.8, but project set to 1.7.