A flat namespace is a bit problematic :- for example: is "containsregexp" a filter, condition or a selector
The antlib proposal does provide associating the same name to different classes using roles. If a flat namespace is used, there is not much point in proceeding with the xml based descriptors. A patch in bugzilla report 17844 provides a simple alternative (it is however missing needed tasks like antlib and antjar). Peter. On Tuesday 22 April 2003 17:13, Stefan Bodewig wrote: > On Tue, 22 Apr 2003, Dominique Devienne <[EMAIL PROTECTED]> wrote: > > I agree with Stefan. > > Cool. > > Now if only I could find time to respond to Antoine's original mail. > 8-) Will try very hard tomorrow. > > > Regarding AntLib itself, XML descriptor or not, I'm more interested > > in being able to partition the namespace used by Ant to perform the > > name to class mapping currently restricted to tasks/types. > > Let's start with tasks and types and see if/how that flies. > > If we want to extend the plugability to mappers or selectors or > whatever (I do), the solution in the end may be a flat namespace > (everything is a type) as Costin seems to hint at when he wants to > drop the difference between task and type. > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
