From: Dennis S. <dm...@so...> - 2005-04-12 23:17:59
|
I think this occurred with Beta 3c when you didn't include the jibx-run.jar in the classpath set inside the bind task. This should be corrected with RC0, so that you no longer need to include anything on the inner classpath except your own classes (one of the many cleanup items that have gone into RC0). - Dennis Paul Tomsic wrote: >here's the relevant parts of my build.xml: ><property name="build.dest" >value="${basedir}/build/classes"/> ><path id="bind.tools.class.path"> ><pathelement location="${basedir}/lib/bcel.jar"/> ><pathelement location="${basedir}/lib/jibx-bind.jar"/> ><pathelement location="${basedir}/lib/jibx-run.jar"/> ><pathelement location="${basedir}/lib/xpp3.jar"/> ><pathelement >location="${basedir}/lib/dom4j-1.5.2.jar"/> ></path> > ><target name="bind" depends="compile, about"> ><bind verbose="true" load="true"> ><bindingfileset dir="${bind.src.dir}"/> ><classpathset dir="${build.dest}"/> ></bind> ></target> > > >and the output: >[bind] Using the following paths: >[bind] home/build/classes >[bind] Using the following binding paths: >[bind] home/binding/binding.xml >[bind] Running binding compiler version jibx-beta3c > >BUILD FAILED >java.lang;ExceptionInInitializerError > > > >any thoughts? > > > > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >_______________________________________________ >jibx-users mailing list >jib...@li... >https://lists.sourceforge.net/lists/listinfo/jibx-users > > > |