> From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > > I can imagine that antlibs would require third party > libraries that might or might not be present. But yes, I > agree with the general idea, I might just want to decouple it > from Ant itself. We probably can take an Ant installation of > a recent version as something that is a requirement for > Antlib developers. >
To me the greatest advantage of such a reorganization is having separate development cycles for all these components. It would create a much more stable ANT core. Simpler to maintain and upgrade. And give more chance for people to experiment with new ways of providing functionality. > > I already have the extension to subant to dynamically infer > the build > > order to use to call the sub-projects in a flexible way > (all you need > > is some XML file stating the sub-project's dependencies). > > A <buildpath> task is on my TODO list, unfortunately I barely > manage to keep track of the items I have to add, not to speak > of addressing them. > If I remember correctly, someone not long ago published an XML format and task simillar to maven's stuff to track and load dependencies. Maybe we should think on having something like that as part of core. > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
