SV: [jdom-interest] Anything else for beta 9?

Bradley S. Huffman hip at a.cs.okstate.edu
Sun Apr 6 16:46:21 PDT 2003


"Per Norrman" writes:

> The Ant/Junit mess:
> 
> I'm definitely not an Ant/Junit master, but what you're experiencing is
> documented here:=20
> http://ant.apache.org/faq.html#delegating-classloader
> 
> The trick is to force JUnit core classes and the JUnit Ant task to be =
> loaded
> by the same class loader (or classloder hierarchy).
> 
> One solution is to add junit.jar to the local classpath in=20
> build.bat/build.sh.


Did that, here's my classpath settings in build.sh

LOCALCLASSPATH=${JAVA_HOME}/lib/tools.jar
LOCALCLASSPATH=${LOCALCLASSPATH}${PS}${JAVA_HOME}/lib/dev.jar
LOCALCLASSPATH=${LOCALCLASSPATH}${PS}../jdom/lib/ant.jar
LOCALCLASSPATH=${LOCALCLASSPATH}${PS}../jdom/lib/xml-apis.jar
LOCALCLASSPATH=${LOCALCLASSPATH}${PS}../jdom/lib/xerces.jar
LOCALCLASSPATH=${LOCALCLASSPATH}${PS}./lib/optional.jar
LOCALCLASSPATH=${LOCALCLASSPATH}${PS}./lib/junit.jar
ANT_HOME=../jdom/lib

However on this Solaris box this then gave a "Process fork failed" on
line 237 of build.xml, which is the <junit> line.  Changing the fork="yes"
to fork="no" in the <batchtext> enclosed by the <junit> tag and at least
build.sh test started working.

Brad



More information about the jdom-interest mailing list