>-----Original Message----- >From: Geir Magnusson Jr. [ mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] >> The ant shell script builds up a classpath appropriate for running ant, >> and this classpath is used by the <javac> task. An interesting >> experiment is to issue the command: >> >> ant -Dbuild.sysclasspath=ignore jar >> >> This causes all sorts of non-existent entity errors. I'm not 100% >> certain this is a fair test, but the netbeans build environment sets the >> build.sysclasspath=ignore ant property. The given reason is that a build >> script should include only known things in a classpath for compiling,
>> and the classpath built up by ant is not a fixed and known thing. >> > >It is for our script :) > >I think this is the same thing that gump does, putting the dependencies into >the classpath, and then having ant use that rather than what the script >builds up... > >Are we on the right track now? Yes, we are on the right track now. The question is, should something be done about this, or should the build script be left alone to depend on what ant puts in the classpath? Experimentation using -Dbuild.sysclasspath=ignore showed that ant.jar and crimson.jar are in the ant classpath, and depended on by Velocity. The things that depend on these are AnakiaTask.java, WebMacro.java, and Texen.java. I observe the build/lib directory contains all the .jar files needed to build Velocity, however it does not contain these two .jar files. Should it contain these .jar files for the purpose of build? If it did, the problem would be solved. I don't know anything about gump, however I would guess from the description that it controls the classpath given to a build very tightly. Richard Hensley mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > -----Original Message----- > From: Jon Stevens [ mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> < mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > ] > > on 11/14/01 11:37 AM, "Hensley, Richard" <[EMAIL PROTECTED]> > wrote: > >> The suggestion from the netbeans users forum was the build.xml for >> velocity was not created in a portable way because it depended on the >> classpath being generated by the ant shell script for a successful >> compile. > > This may be true of an older version of Velocity, but is not true for > the > version in CVS or the latest rc releases as we don't have the shell > scripts > in CVS any longer (they have been removed). > > (p.s. BTW, Geir, could you please announce releases on the -dev list as > well?) > > -jon
