JIBX is nicely divided up into JARs, each of which serves a precise purpose and is required in different phases of the code life cycle.
For example, the jibx-run.jar is the only one which is required at run-time, and you do not need to include it at compile-time (Maven terms).
This is great stuff, which unfortunately is broken by maven-jibx-plugin, which requires (AFAIKT) the jibx-run JAR to be included as a compile-time dependency.
I have tried:
1) Only including jibx-run.jar as a run-time dependency (not listed in the attached file): I get an error when running "mvn jibx:bind" because classes from jibx-run.jar are not available.
2) Including jibx-run.jar as a build extension (this is (A) in the attached file): Same error as 1.
3) Including jibx-run.jar as a plugin dependency (this is (B) in the attached file): Same error as 1.
There is of course the workaround of simply changing the scope of the dependency ("C" in the attached file) to "compile", but this would make jibx-run.jar classes available in my code, which is undesirable.
Why isn't the jibx-run.jar included in maven-jibx-plugin - the other jibx JARs seem to be?