That seems like a great idea. The current instructions were created by me, and I am hardly an ant expert. I thought I was doing good to put the jars in my home dir -- prior to that, we used to tell people to smash their ant install! (Which always failed for me because I tried to use the ant that came with OS X, so my ant config would be wiped out every time OS X updated.)
Clearly it's better to pass requisite jars in the narrowest scope possible (like, only when we actually need them). On 2011-12-10, at 10:08, Raju Bitter wrote: > I think the Subversion build instructions should be improved in some points: > > Adding the JAR files required for Ant to $HOME/.ant/lib polluted my > Ant environment for the Google Closure compiler build (Closure uses a > custom version of Rhino). > > The Google Closure Ant build, for example, adds the JAR files to the > <path> elements, e.g. > http://code.google.com/p/closure-compiler/source/browse/trunk/build.xml > <path id="srcclasspath.path"> > <pathelement location="${classes.dir}" /> > <fileset dir="${lib.dir}"> > <include name="args4j.jar"/> > <include name="guava.jar"/> > <include name="json.jar"/> > <include name="jsr305.jar"/> > <include name="protobuf-java.jar"/> > </fileset> > <fileset dir="${buildlib.dir}"> > <include name="rhino.jar"/> > </fileset> > </path> > > That would be the better solution for OpenLaszlo as well, wouldn't it? > I normally install a custom version of Ant, next to the one already > available through the OS. If the Ant version of the OS is updated, I > don't need to worry about possible conflicts with the Ant setup for my > OpenLaszlo build. Any comments?
