> From: Costin Manolache [mailto:[EMAIL PROTECTED] > > Erik Hatcher wrote: > > > > > But the current one does not support adding other components like > > conditions, mappers, filters, and selectors. > > Does ant support this ? > > And what do you mean "does not support adding" ? It can add > any component > ( as datatype for example), and nothing stops you from using > any datatype as > anything you want ( condition, mapper, filter or selector ). >
The big difference is the way ANT currently treats a core condition/mapper/filter from one defined by a user. If I look at a build file the syntax are completely different, not only that but in some cases the name of attributes changes for the same class depending on whether I use the core syntax or the syntax for user defined implementations. And it is not only the things above, it is also the vendor specific elements of things like <ejbjar> <jspc> and others. I would like those classes reemplemented using roles and scatter the vendor specific code to the wind (to te vendors) where it belongs (on their own release cycle). To me the whole point of antlib is that it will make core code and 3rd party maintained components completely indistinguishable from the point of view of the build writer, no priviledges to anyone. Jose Alberto
