ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Cohen <>
Subject Re: New Launcher and JPackage RPMs
Date Fri, 16 Jan 2004 17:18:25 GMT
Well, we at commons-net would have been rushing the release to meet ant's 
"deadline" and there are internal refactorings which we would have liked to 
have included that we were planning to postpone in the rush, but now will 
take the time to get right, so I doubt that commons-net-1.2.0 will be done in 
time for ant 1.6.1 and therefore we shouldn't update the ant manual just yet. 

I think the best procedure will be for commons-net to work at it's own best 
pace and when it's done, notify the ant list, via bugzilla and via posts to 
the ant-dev and ant-user lists.  At that point, any ant users needing this 
functionality would be able to grab the commons-net-1.2.0 jar and get the 
basic functionality.  At that point also, coding could begin on the HEAD 
branch of ant and the documentation in time for 1.7 (or maybe 1.6.2 if that 
comes to pass).

On Friday 16 January 2004 9:31 am, Antoine Lévy-Lambert wrote:
> Peter Reilly wrote:
> > Antoine Lévy-Lambert wrote:
> >> I am +1 to get this into ant 1.6.1.
> >
> > (in relation to static map of jarfile->manifest class path in
> > AntClassLoader2).
> >
> > Ok I will commit that.
> >
> > Another optimization I tried was a quick hack to DefBase to have a
> > static field containing the default classloader, so it
> > gets set once.  This did speed up the typedef the second and
> > subsequent times and reduced the
> > time for the test to 1.6 second (from 3 and thus below the 1.5.4 times
> > (2 second) when using the crimson xml parser).
> Sounds useful.
> > However it is a complete hack, and does not deal with non-default
> > classpaths  like:
> > <typedef classpath="${antlib.jar}"
> > resource="net/sf/antcontrib/"/>
> Do you mean : your change is bringing an optimization for taskdefs which
> are done based on jars which have already been loaded by the launcher,
> presumably because they are in $ANT_HOME/lib or in a -lib directory  ?
> And not if the taskdef is requiring extra jars or directories which were
> not included when ant got started ?
> Cheers,
> Antoine
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message