Return-Path: 
 <dev-return-55270-apmail-ant-dev-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-dev-archive@www.apache.org
Received: (qmail 66250 invoked from network); 10 Feb 2004 17:10:59 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 10 Feb 2004 17:10:59 -0000
Received: (qmail 20174 invoked by uid 500); 10 Feb 2004 17:10:15 -0000
Delivered-To: apmail-ant-dev-archive@ant.apache.org
Received: (qmail 20086 invoked by uid 500); 10 Feb 2004 17:10:14 -0000
Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@ant.apache.org>
List-Subscribe: <mailto:dev-subscribe@ant.apache.org>
List-Help: <mailto:dev-help@ant.apache.org>
List-Post: <mailto:dev@ant.apache.org>
List-Id: "Ant Developers List" <dev.ant.apache.org>
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Delivered-To: mailing list dev@ant.apache.org
Received: (qmail 20011 invoked from network); 10 Feb 2004 17:10:13 -0000
Received: from unknown (HELO web20420.mail.yahoo.com) (66.163.169.96)
  by daedalus.apache.org with SMTP; 10 Feb 2004 17:10:13 -0000
Message-ID: <20040210171014.48125.qmail@web20420.mail.yahoo.com>
Received: from [208.128.243.52] by web20408.mail.yahoo.com via HTTP;
 Tue, 10 Feb 2004 09:10:14 PST
Date: Tue, 10 Feb 2004 09:10:14 -0800 (PST)
From: Matt Benson <gudnabrsam@yahoo.com>
Subject: RE: multi-result <mapper>s
To: Ant Developers List <dev@ant.apache.org>
In-Reply-To: <F3D701FEF0483B4AAA11A18CE328461B078182@leeds.cellectivity.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

--- Jose Alberto Fernandez <jalberto@cellectivity.com>
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: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org