Hi all, We're having some troubles with dependencies while building a binding component. The problem is that some of the dependencies are packaged with the BC but some are not. Here's what "mvn dependency:tree" shows: (removed some unnecessary parts of the output) [INFO] +- xpp3:xpp3:jar:1.1.4c:compile [INFO] +- log4j:log4j:jar:1.2.14:compile [INFO] +- junit:junit:jar:4.7:test [INFO] +- org.jacorb:jacorb:jar:2.3.1:compile [INFO] | +- org.antlr:antlr:jar:3.2:compile [INFO] | | \- org.antlr:antlr-runtime:jar:3.2:compile [INFO] | | \- org.antlr:stringtemplate:jar:3.2:compile [INFO] | | \- antlr:antlr:jar:2.7.7:compile [INFO] | +- backport-util-concurrent:backport-util-concurrent:jar:2.2:compile [INFO] | +- org.slf4j:slf4j-api:jar:1.5.8:compile [INFO] | +- org.slf4j:slf4j-jdk14:jar:1.5.8:compile [INFO] | +- logkit:logkit:jar:2.0:compile [INFO] | \- picocontainer:picocontainer:jar:1.2:compile [INFO] | \- xml-apis:xml-apis:jar:1.0.b2:compile
In our case now, e.g. log4j and xpp3 libs are bundled with the resulted BC installer, but JacORB (and it's dependecies) are not. We've verified that all the dependencies are really available and deployed in local repo. All have pom files also within the local repo as well as sha1 checksum files. Both 4.2 and 4.3 versions of the plugin seems to have same results. Any ideas what's causing this? Cheers, - Jussi -
