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] - <pathconvert> should support nested <mapper>s in addition to its <map> element
Date Sun, 25 Jan 2004 17:06:18 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

<pathconvert> should support nested <mapper>s in addition to its <map> element





------- Additional Comments From gudnabrsam@yahoo.com  2004-01-25 17:06 -------
I believe my last comment was not completely correct, due to the fact that each 
<map> element passes the path element through unchanged if its prefix does not 
match the from attribute, while mappers return null for files that do not 
match.  In another thread (<a href="http://marc.theaimsgroup.com/?l=ant-
user&w=2&r=1&s=%3Capply+executable%3E+question+&q=b">link</a>), I
discussed 
with Stefan the idea of creating a <mapper type="composite"> to wrap other 
mappers.  In implementing that, I have discovered it and this enhancement to be 
complimentary, especially because using a nested <mapper> with <pathconvert> is

a very nice way to test any <mapper>.  Because the enhancements will be 
complimentary I plan, when they are complete, to roll them all into this one 
enhancement report.

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


Mime
View raw message