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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
