ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Phil Weighill-Smith <>
Subject Re: Proposal
Date Tue, 25 Jan 2005 09:42:20 GMT
My guess is that, because of backward compatibility, the "ant" startup
scripts won't get changed to unset it (which they could do easily
enough). Some people use the classpath to actually add extra libraries
to Ant because of historical needs (yes, there are better means of doing
so now).

Some documentation stating that there can be issues, and that people
should check what their class path is if they have trouble running Ant,
would be a good thing. Other than that, use a crutch or persuade someone
that backwards compatibility isn't so critical in this case (or to add a
special "use environment's class path" option to Ant's invocation to
allow for backwards compatibility).

Phil :n.

On Tue, 2005-01-25 at 09:37, Kev Jackson wrote:

> Phil Weighill-Smith wrote:
> >On Tue, 2005-01-25 at 09:22, Erik Hatcher wrote:
> >
> >  
> >
> >>You may consider creating a custom ant command script which unsets 
> >>CLASSPATH before invoking the executable class.
> >>
> >>    
> >>
> >
> >
> >Exactly what we do!
> >  
> >
> <rant>My point was that it shouldn't be set in the first place, 
> unsetting it before running is good, but it's a crutch.  The developers 
> shouldn't have it set in the first place</rant>  Oh and Oracle setting 
> it is no excuse as they have been told to uninstall the damn Oracle 
> client on many many occasions
> Kev
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Phil Weighill-Smith <>
Volantis Systems

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message