I didn't explain myself clearly. I use the ant shell script from an ant-1.4.1 install, and the build.xml that is present in the build directory for Velocity. I use this because it is indicated in the README.txt file. I issue the following command to build from the command line:
ant jar 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. Richard Hensley mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> -----Original Message----- From: Jon Stevens [ 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 -- To unsubscribe, e-mail: < mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: < mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >
