ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject AW: commons dev list CVS component
Date Tue, 09 Aug 2005 09:42:49 GMT
ATM tasks and types are declared via taskdefs/ and types/
Could we extend that mechanism to allow an AntLib-URI?

# standard ant tasks 
# AntLib's
# Standard external


>-----Urspr√ľngliche Nachricht-----
>Von: Kev Jackson [] 
>Gesendet: Dienstag, 9. August 2005 11:27
>An: Ant Developers List
>Betreff: Re: commons dev list CVS component
>>I would love to remove some of the fat from the current ANT and move 
>>more things to individual antlibs that people can load on demand.
>>However, the main issue we need to face is how to maintain easy 
>>backward compatibility at least at the XML level.
>>We need to define a proper strategy or antlib definition pattern that 
>>allows an installation of ANT to dump a bunch of antlibs 
>somewhere and 
>>the corresponding tasks can be used just as if they where defined in 
>>CORE (without any need to declare or use additional name-spaces).
>>If we solved this issue satisfactorily, we could reorganize 
>the entire 
>>set of CORE and optional tasks allowing for separate releases for 
>>optional components.
>>And hence allowing for a much more stable CORE and uptodate libraries.
>>Jose Alberto
>+1 exactly
>To unsubscribe, e-mail: For 
>additional commands, e-mail:

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

View raw message