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 18128] - Dependset srcfileset does not handle absolute path
Date Wed, 19 Mar 2003 22:44:48 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=18128>.
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=18128

Dependset srcfileset does not handle absolute path





------- Additional Comments From peter.reilly@corvil.com  2003-03-19 22:44 -------
I have just tried an experiment on my dos box:
<project name="fileset" default="t">
    <target name="t">
        <mkdir dir="e:\test"/>
        <touch file="e:\test\a.b"/>
        <fileset id="f1" dir="e:/" includes="test\a.b"/>
        <pathconvert targetos="windows" property="p1" refid="f1"/>
        <echo message="p1 is ${p1}"/>
        <fileset id="f2" dir="e:\" includes="\test\a.b"/>
        <pathconvert targetos="windows" property="p2" refid="f2"/>
        <echo message="p2 is ${p2}"/>
        <fileset id="f3" dir="e:" includes="\test\a.b"/>
        <pathconvert targetos="windows" property="p3" refid="f3"/>
        <echo message="p3 is ${p3}"/>
        <fileset id="f4" dir="e:" includes="test\a.b"/>
        <pathconvert targetos="windows" property="p4" refid="f4"/>
        <echo message="p4 is ${p4}"/>
    </target>
</project>
This gives the following result:

Buildfile: c:\cygwin\home\peter\learning\fileset\build.xml

t:
p1 is E:\test\a.b
p2 is 
p3 is 
p4 is E:\test\a.b

The manual page on fileset contains the following:

"FileSets are groups of files. These files can be found in a directory tree
starting in a base directory"

As windows has muliple roots and one can only specify one root to a fileset,
I can conclude that is it impossible to use fileset in the manner you are
trying to use it. Fileset in this case is working as defined and this report
is not a bug - but maybe is an enhancement request.

Mime
View raw message