You still need mechanisms to allow the developer to override the default
decisions checked in to the build scripts. For nearly all of the "I've checked
in jars for the convenience of developers" packages I've evaluated for use fail
to allow such overrides, and hard code their build classpaths to point at the
checked in JARs only.
Well, we should address bad build file writing more than JAR's in CVS! :) My build files follow this scheme <http://www.ehatchersolutions.com/JavaDevWithAnt/ant.html#lib> - and I have an Ant property for *each* JAR that can be easily overridden at many levels.
Erik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
