On 18 January 2011 11:36, sebb <seb...@gmail.com> wrote: > On 18 January 2011 11:20, Stefan Bodewig <bode...@apache.org> wrote: >> On 2011-01-13, sebb wrote: >> >>> On 10 January 2011 20:26, sebb <seb...@gmail.com> wrote: >>>> On 10 January 2011 12:23, Stefan Bodewig <bode...@apache.org> wrote: >> >>>>> It likely is part of xalan.jar which is present in -Xbootclaspath but >>>>> not CLASSPATH. >> >>> How does one add Xalan to the build classpath? The JMeter project >>> depends on Xalan, but it does not seem to get added to the classpath, >>> only the bootclasspath. >> >> It should be going into the forked VM's bootclasspath via Ant's >> build.sysclasspath. If this is not the case then something inside Ant >> has been broken. > > So Xalan is handled differently from other dependencies? > >> Right now I don't have the time to follow this through. I suspect newer >> OpenJDKs no longer use the system property "sun.boot.class.path" but >> rather something new without "sun" in its name to provide the >> bootclasspath to the running application. If so Ant's >> Path.systemBootClasspath ends up empty and can't be propagated to the >> forked VM. Ant would need to get fixed which in turn should fix the >> Gump build (likely Forrest's as well) since Gump uses Ant's trunk. > > And maybe BSF3 as well... > >> I don't know when I'll have the cycles to confirm my suspicion, sorry. > > OK, no problem. > > I can try adding some debugging to the build file.
Ant is not passing -bootclasspath to the forked <java> task that runs the test. Adding the Xalan jars to the test run using <work parent=""> references fixes the problem by adding the jars to the test classpath. However, this is a bit messy, as the paths may perhaps change. Just tried adding clonevm="true" to the <java> task, but that causes problems for non-Gump builds. I'm beginning to think this may be a Gump bug: although Xalan is listed as a normal dependency, it is not added to the classpath, only to the bootclasspath. >> Stefan >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@gump.apache.org >> For additional commands, e-mail: general-h...@gump.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
