From: Martin A. <mar...@go...> - 2005-05-05 08:17:55
|
Hi Gary, as I implemented it, it converts scanned files from first fileset to full path asis includes. So <fileset id="foo1" basedir="X:\nant\t1"> <include name="world.peace" /> <include name="world.war"/> </fileset> <fileset id="foo2" basedir="X:\nant\t1"> <includesfileset refid="foo1"/> <exclude name="world.war"/> <include name="reefer.saddness" /> </fileset> becomes <fileset id="foo2" basedir="X:\nant\t1"> <include asis="true" name="X:\nant\t1\world.peace"/> <include asis="true" name="X:\nant\t1\world.war"/> <exclude name="world.war"/> <include name="reefer.saddness" /> </fileset> To your question with excludes: - all excludes in foo1 are respected. - no exclude in foo2 take effect on included files. Thats something which is already in place. Excludes do _not_ affect asis includes. It sounds a little strange to me, but I'd rather not change something what is in place for several years. Is this behaviour right? Maybe yes. I think about <includesfileset> like fileset merging operation - so you merge existing fileset with some include/exclude mask. But I see, there is no way how to filter out existing fileset to another one... So maybe its not right way? Ideas? Note: reason why I used asis is to prevent double-scan. asis includes are not scanned anymore, and all included files via includesfileset was scanned once already. Martin Aliger |