Maybe this has been addressed, but I couldn't find it in the list archives.
I noticed that since 12.2.0, jmol has not listed any dependencies in the
maven pom file, but instead it includes them directly in the jar file. This
has the effect of breaking maven's dependency resolution for project which
include both jmol and its dependencies. I found that out the hard way
through some very odd classpath errors in a project that declared a
commons-cli:1.2 dependency but which was actually loading the 1.0 classes
from the jmol jar.
I assume the reason that the dependencies were bundled together was to
allow a stand-alone jar to be distributed. This can be supported by
building two profiles: a standard jar which does not include dependencies
and that gets uploaded to the maven repo; and a distribution jar which gets
built using the maven-shade-plugin in order to include all dependencies,
and which gets distributed via the website.
-Spencer
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users
