ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 26364] - [PATCH] nested <mapper> for <pathconvert> PLUS composite <mapper>
Date Tue, 03 Feb 2004 16:40:53 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26364>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26364

[PATCH] nested <mapper> for <pathconvert> PLUS composite <mapper>





------- Additional Comments From peter.reilly@corvil.com  2004-02-03 16:40 -------
Using dynamic configuration to set the attributes of the embedded filename
mapper class is a good idea.

The <globmapper> may be used with custom tasks. It can only be used
as an nested element to a <mapper> element. For example the <copy> task
can use it without any modification, as can the <outofdate> task from
ant-contrib.

On a general note, I never liked the design of mapper + filename mapper
being one element with the specific filename mapper being specified by
an attribute. This is different from the other customizer types - like
selectors, filters and conditions. The mapper patch will allow new custom
file name mappers to be defined and used like built-in mappers - as nested
types in a <mapper> container, deprecating the current type="x/y/z" usage.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message