gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <bode...@apache.org>
Subject Re: build of avalon on gump
Date Fri, 20 Feb 2004 09:39:51 GMT
On Fri, 20 Feb 2004, Leo Simons <leosimons@apache.org> wrote:

> There's a classloader issue of some kind.

Note that it passes on "traditional" Gump.  Both on my installation
and on gump.covalent.net.

I'm trying to figure out the difference in CLASSPATH here.  This is
what "traditional" Gump uses:

export CLASSPATH=$CP:$JAVA_HOME/lib/tools.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/avalon/framework/target/classes
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/avalon/framework/target/api-classes
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/avalon/framework/target/impl-classes
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/avalon/framework/target/test-classes
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/ant/dist/lib/ant.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/ant/dist/lib/ant-launcher.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/ant/dist/lib/ant-jmf.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/ant/dist/lib/ant-junit.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/ant/dist/lib/ant-stylebook.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/ant/dist/lib/ant-swing.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/ant/dist/lib/ant-trax.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/ant/dist/lib/ant-xalan2.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/ant/dist/lib/ant-nodeps.jar
export CLASSPATH=/home/bodewig/dev/gump/xml-xalan/java/build/xalan-unbundled.jar:$CLASSPATH
export CLASSPATH=/home/bodewig/dev/gump/xml-xerces2/java/build/xercesImpl.jar:$CLASSPATH
export CLASSPATH=/home/bodewig/dev/gump/xml-xerces2/java/build/xmlParserAPIs.jar:$CLASSPATH
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/dist/junit/junit.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-log4j/log4j-20040219.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-log4j/log4j-lf5-20040219.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/jakarta-log4j/log4j-chainsaw-20040219.jar
export CLASSPATH=$CLASSPATH:/home/bodewig/dev/gump/avalon-logkit/build/lib/logkit.jar
export CLASSPATH=/home/bodewig/dev/gump/xml-commons/java/external/build/xml-apis.jar:$CLASSPATH

and

-Xbootclasspath/p:/home/bodewig/dev/gump/xml-xalan/java/build/xalan-unbundled.jar:/home/bodewig/dev/gump/xml-xerces2/java/build/xercesImpl.jar:/home/bodewig/dev/gump/xml-xerces2/java/build/xmlParserAPIs.jar:/home/bodewig/dev/gump/xml-commons/java/external/build/xml-apis.jar

The only difference I can see compared to the LSD result page is the
order of the Ant and Log4J jars as well as the order of the
bootclasspath (and the bootclasspath stuff is not repeated in
CLASSPATH on LSD).

CascadingError should be picked up from
avalon/framework/target/classes, I don't see why it doesn't.

Wait, maybe we need a <mkdir> for it?  I can't really say under which
circumstances one needs a <mkdir> for <work> and when it is optional,
but this is something we should try.

Stefan

Mime
View raw message