https://bz.apache.org/bugzilla/show_bug.cgi?id=67621
Stefan Bodewig <bode...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS| |All
--- Comment #1 from Stefan Bodewig <bode...@apache.org> ---
mappedresources is doing something quite different from what you expect it to
do.
What it really does is it returns the very same resources that have been part
of the resource collection wrapped (the directories contained in your PATH) and
only act as if their name was different. But something like <exists> would
still look at the directories and just tell you whether the directory exists,
not if it contains find.
That the mapper is applied to the base name of the directory that is part of
the PATH rather than the absolute path is something that surprises myself today
- but likely has been the logical choice a long time ago.
Do you really need to find the find command or is it enough to know whether
find is on your PATH so you can execute t? In the latter case
<available property="find.found" file="find" filepath="{env.PATH}"/>
would work,
--
You are receiving this mail because:
You are the assignee for the bug.
