--- Jose Alberto Fernandez <[EMAIL PROTECTED]> wrote: > rather than creating yet another way for mappers, > we should do best by starting working on 1.7's > features so we try to converge to a unified model.
Are you meaning that <typedef>ing FileNameMappers is but a small part of something that needs to be done on a grand scale for 1.7? Fine by me. > It would mean that mappers can be in their own > antlib library, > use their owm NameSpace and all the other goodies of > the model. Are you talking about custom mappers? Sticking core mappers into a separate namespace feels kind of funny to me. Not exactly wrong, but my BC sense is tingling... I'm sure that can't be the whole story. > > > I believe that is the aim for 1.7 with the > > > add(Interface) > > > methods. > This are new instrospection methods so that > Conditions, mappers, etc > can be added and made available to all tasks > automagically. > They are suppose to be part of 1.7. Do these methods exist in some form in the current codebase or are they still in a planning phase? Are you touching on the "role" concept here? I've been wanting to know more about that. -Matt __________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
