ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominique Devienne <>
Subject RE: optional task jars
Date Tue, 20 Jul 2004 19:55:25 GMT
> -----Original Message-----
> From: Nicolas Mailhot []
> One of the patches we apply at jpackage consists of defining an env var
> that is added to the ant classpath (and can be defined in the ~/.antrc
> for example).
> The default ant/lib is almost empty and we discourage its use - if the
> user does not define the classpath variable a default system-wide value
> is used instead.
> The reason we do it this way is any user can tweak the classpath his ant
> will use instance, jars are not mindlessly duplicated all over the place
> in private lib dirs, and jar ordering is defined (this last being more a
> positive side-effect than a design target, relying on jar ordering is
> dangerous practise but sometime people need it).
> I must admit I toyed a moment with a ~/.ant/lib but (apart from being a
> bit more difficult to implement) it seemed very awkward to use.
> I don't know if it's ever been merged upstream - probably not, since we
> do not use a traditional classpath format, but our own simplified
> notation that is fed to a routine that searches actual jar location on
> the system to assemble a classic classpath.

My only comment to this is that when we started developing our java stuff on
Linux, the Ant version installed on Linux (thru some developer package) just
conflicted with our CVS-controlled centralized platform-independent Ant
version. We advice our developers to get rid of that Ant version on Linux,
and I also reset the CLASSPATH before calling Ant, just in case they don't.
I much prefer the normal Ant distro myself, on any platform. --DD

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message