I think we are now in the new world of ANT 1.6 (the wold of namespaces and antlibs). We should stride to focus our efforts so that all our extension points (of all sorts) follow the antlibs/typedef approach and move away from having property files with magic names defining special types.
I believe that is the aim for 1.7 with the add(Interface) methods. Jose Alberto > -----Original Message----- > From: Matt Benson [mailto:[EMAIL PROTECTED] > Sent: 09 February 2004 23:23 > To: Ant Developers List > Subject: multi-result <mapper>s > > > Stefan and I talked about doing one of these here: > > http://marc.theaimsgroup.com/?l=ant-user&m=107487826503877&w=2 > > Peter and I each produced a different implementation. > See > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26364 > for our discussion. In the end Peter's changes are > probably more powerful than mine but his specific > implementation represents a paradigm shift, hence our > decision to start a thread devoted to the issue. > > <mapper>s have always been specified via a <mapper> > element and either a "type" or "classname" attribute, > which actually specified an implementation of > FileNameMapper. Peter's proposition allows to define > the implementation type directly in > types/defaults.properties, then nest these directly > into the <mapper> element. In this way <mapper>s > would/could look a lot more like <condition>s and > <selector>s, especially when ref'd. Another note is > that adding new core mappers would be a properties > file (or other typedef) edit rather than a change to > an EnumeratedAttribute. Finally, this allows more > specialized attributes on mappers than just "to" and > "from". So... does anyone have a problem with > changing the recommended usage of <mapper>s while > maintaining BC? > > -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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
