ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject AW: AW: AW: commons dev list CVS component
Date Tue, 09 Aug 2005 08:26:27 GMT
We dont have any scenarios for the 1.7-release and AntLibs. AntLibs are brand new (for the
But I think we tend to split the current codebase into AntLibs, so we wont do the opposite
for svn.

What we do internally doesnt met (so much).
The user (users who use Ant or writing against Ants API) shouldnt be forced to do any. The
the bin-distro and that´s all. All core/optional tasks work as before and all jar´s are
in /lib.

Maybe the src-distro would be reorganized. But a "ant build" should resolve that.


>-----Ursprüngliche Nachricht-----
>Von: Kev Jackson [] 
>Gesendet: Dienstag, 9. August 2005 09:59
>An: Ant Developers List
>Betreff: Re: AW: AW: commons dev list CVS component
> wrote:
>>Holding the source in an AntLib doesnt mean that we cant ship them in 
>>the "main" distro (nearly) as usual.
>Indeed, we just need to make the task point to the re-packaged 
>versions instead, I presume we'll ship the svn task as part of 
>verions 1.7 as an antlib?
>To unsubscribe, e-mail: For 
>additional commands, e-mail:

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

View raw message