Re: Antlib... when?

[Erik Hatcher]

Just for the record, I'm working on XDoclet subtasks at the moment and 
refactoring the proposal/xdocs stuff and migrating it to live within 
the XDoclet codebase.  This will allow third-party task writers to use 
XDoclet and generate "descriptors" for their tasks/datatypes easily.  
The descriptors are currently planned for documentation, but have use 
for part of this discovery mechanism as well as for IDE's and other 
tools that wrap Ant to learn about what the tasks/types support by 
looking at the embedded descriptors.

How shall we compare notes and see if what I'm doing applies to Antlib 
needs?  I'll hopefully be committing my stuff into XDoclet's CVS soon.  
Its taken me a while to get it converted to the new XDoclet API and get 
back into the swing of things with it, my apologies.  But I'm now 
actively working on it and progress is being made by the minute.

        Erik

On Saturday, January 4, 2003, at 08:57  AM, Nicola Ken Barozzi wrote:
Any idea on when some sort of Antlib system will be setup?
The DiscoveryTask is a step in the right direction, but a much simpler 
system without additional dependencies can be set up for a simple 
use-case.

Instead of loading "default" properties from a file in the ant.jar, we 
can do it for all jars in ${ant.home}/lib. This would make it simple 
to move the declarations out of the ant.jar and add "default" tasks to 
the run.

Could this be a simple option to use?
--
Nicola Ken Barozzi                   [EMAIL PROTECTED]
            - verba volant, scripta manent -
   (discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail:   
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: 
<mailto:[EMAIL PROTECTED]>



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>