> From: Erik Hatcher [mailto:[EMAIL PROTECTED]
> 
> > - maybe we want antlibs to have some initialization. This can be 
> > easily done
> > by allowing more ant elements in the descriptor
> > - maybe we'll want to allow antlib to declare targets - 
> that could be 
> > used
> > in depends or antcall ( <target name="foo"
> > depends="myAntLib:antlibTarget"/> ).
> 
> Wow.... ok, still pondering....
> 
> > Again - those are just examples, there are a lot of things 
> that could 
> > be
> > done easily. Even if you don't need any of this - it would 
> be nice to
> > not have to repeat the long and painfull evolution of the main xml
> > processor.
> 
> It'll take some thinking and convincing for me to see why 
> antlib needs 
> descriptors that get processed like Ant build files.  Something as 
> simple as Digester would seem to do the trick (bootstrap 
> craziness?!)  
> but as I said, I want to see what others think and let myself 
> consider 
> your idea a bit more.
> 

I am not too keen on having alive ANTS roaming in my classpath.

Jar files are passive things, in general having too many in your
classpath does not mean you will execute more stuff. I think that is nice
and autoinitializing jars (antlibs) sound way too scary at this point.

Jose Alberto

Reply via email to