|
I've also bumped into this issue. Currently project classpath entries are being added to JiBX bindAll classpath, but it turns out that they are being added incorrectly (see attached 'wrong-classpath.txt').
There are two problems:
1. Relative paths (e.g. 'lib/jibx-extras.jar') are prepended with project name and the result (e.g. '/myproject/lib/jibx-extras.jar') is treated as an absolute path which is wrong.
2. Additional dependencies are being pulled from MANIFEST.MF of jibx-extras.jar. This is generally ok, but these dependencies can be optional and thus missing from project.
I've created a pull request fixing these problems:
https://github.com/jibx/jibx-eclipse/pull/2
After my fix, when given the following set-up:
-
jibx-extras.jar exists in lib folder and is in .classpath
-
jibx-run.jar exists in lib folder but is NOT in .classpath
-
other jars from jibx-extras.jar's MANIFEST.MF do not exist in lib folder
there will be two entries in JiBX bindAll classpath: jibx-extras.jar and jibx-run.jar, both with correct absolute paths (see attached 'right-classpath.txt')
I will contact others to approve my fix
|
