https://bz.apache.org/bugzilla/show_bug.cgi?id=67621

            Bug ID: 67621
           Summary: mappedresources strips paths
           Product: Ant
           Version: unspecified
          Hardware: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core
          Assignee: notifications@ant.apache.org
          Reporter: david.stde...@gmail.com
  Target Milestone: ---

<project>

    <property environment="env" />
    <first id="findcmd">
        <restrict>
            <mappedresources id="paths">
                <path path="${env.PATH}" />
                <filtermapper>
                    <suffixlines suffix="/find" />
                </filtermapper>
            </mappedresources>
            <exists/>
        </restrict>
    </first>

    <echo>
        ${toString:paths}
        ${toString:findcmd}
    </echo>
</project>

     [echo]        
bin/find:bin/find:bin/find:sbin/find:sbin/find:bin/find:bin/find:bin/find:lnx64/find:unx/find:bin/find:lnx64/find:bin/find
     [echo]         bin/find

My expectation of the refid "paths" from the mappedresources would be to get
"full" paths with /find added, not all the paths cut-off at the basename. Is
this a really a bug?

Note: the first/restricts/exists part is my next step in trying to find find
:), but the exists on the mappedresources is kind of meaningless as it doesn't
appear to be treating these resources as actual paths.

Maybe my trouble is in not fully understanding this confusing documentation...
"Even if mappedresources wraps a resource collection that consists of
file-system based resources, mappedresources will not appear to be file-system
based. This means you can't use mappedresources with tasks that only allow
file-system based resources."  

Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to