On Wed, Sep 26, 2001 at 04:01:25PM +0200, Giacomo Pati wrote: [...] > > > > I am currently creating a simple ant task similar to <available> > > > > which checks only the defined classpath and not the parent > > > > classloader. So the LDAPTransformer is only included if the > > > > jar is available in the lib directory. > > > > > > How about ignoring the classpath set by users? Additional features can > > > be compiled in by putting the corresponding jars into the ./lib > > > directory. > > > > > Yes, this is exactly what my ant task does. It seems not possible > > to ignore the classpath set by users with the available task. > > While we have ant installed in the CVS already we can modify the build.sh/.bat > files to ignore the calsspath set by the user.
There's a magic property in Ant (1.4 at least): <property name="build.sysclasspath" value="ignore"/> That prevents tasks from seeing Ant's classpath. That includes: - anything in the user's CLASSPATH (what you want) - anything in $ANT_HOME/lib/*.jar Jars from $ANT_HOME/lib can be added explicitly in <classpath> blocks to tasks which need it. --Jeff > Giacomo [..] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
