Not only is this not as clean as having support for multiple filesets, it also causes problems for tasks that use the relative path to the base directory (like the <zip> task does to determine the directory within the zip file).
Ant supports this in various (all tasks that use filesets ?) tasks.
Rather than modify every task that uses a fileset, is it worth (is it correct?) modifying fileset to be self-nesting?
For example, your references element from above might become:
<references>
<includeset basedir="C:/Test" />
<include name="AssemblyA.dll" />
<include name="bin/AssemblyB.dll" />
<include name="whatever/AssemblyC.dll" />
</includeset>
<includeset basedir="D:/Test/whatever" />
<include name="AssemblyD.dll" />
<include name="AssemblyE.dll" />
</includeset>
</references>or equivalently (slightly more concise):
<references basedir="C:/Test" />
<include name="AssemblyA.dll" />
<include name="bin/AssemblyB.dll" />
<include name="whatever/AssemblyC.dll" />
<includeset basedir="D:/Test/whatever" />
<include name="AssemblyD.dll" />
<include name="AssemblyE.dll" />
</includeset>
</references>You could then play with includesets as required to ensure each included file has the correct relative path.
If this isn't a bad idea, I could probably knock together a prototype next weekend...
Thoughts?
-- Troy
------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
