ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: DO NOT REPLY [Bug 48001] Document differences between tasks' usage of mappers in some fashion.
Date Fri, 16 Oct 2009 06:15:48 GMT
On 2009-10-15, Matt Benson <> wrote:

> It seems that tasks that use mappers usually apply the mapper to a
> resource name; some tasks, like pathconvert, however, apply the mapper
> to the string representation of a resource (e.g. full path for a file
> resource).  Do we consider pathconvert's behavior anomalous enough to
> call it a bug?

I'm not sure.  Given the original use-case of Bugzilla issue 48001 I
would have expected it to work with absolute path names.

mappers should be applied to resource.getName() not toString() in
general, I agree.  Maybe I'm more surprised that the fileset resources
are not returning their full path name as their name then.

Anyway, I agree pathconvert's behavior is anomalous but it probably is
the way it is to preserve backwards compatibility to the pre-resource
collection implementation.

> I am thinking our basic approach should be to document that name-only
> is the usual usage, then document task-level exceptions to this "rule"
> as we encounter them.

Sounds good.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message