I am attempting to use the feature of a <fileset> which allows for an
external reference to a pre-defined fileset. This would be most useful
in my application in cases where a complicated include/exclude filter
needs to be applied to several file and directory operations.
However, the behavior of the 'basedir' attribute is not what I would
expect:
<fileset id="webSiteFileSet">
<include name="*.*" />
<exclude name="*.config" />
<exclude name="database*.xml" />
</fileset>
<target name="PurgeSite" >
<echo message=" PurgeSite = ${PurgeSite_dir}" />
<delete>
<fileset refid="webSiteFileSet"
basedir="${PurgeSite_dir}" />
</delete>
</target>
In this case, I would expect the 'basedir' attribute that I supplied in
the <delete> task to take effect. However, only if the 'basedir'
attribute is specified in the <fileset> definition, will it be properly
applied by the <delete> task.
Is this by design? Is this a bug or oversight? Is there a mechanism
for causing the <delete> task to behave as I am attempting to use it in
the above case?
Thanks,
Ken Parrish
Gomez, Inc.
------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
