I agree - I've been using text files and includesList (just a raw list of asis files) for now, but I think it would be cool to include a build file that had a fileset definition with the set of files you wanted - this could be included at the top of each build file. It should also increase performance for recursive fileset definitions used over and over.

Philip Nelson wrote:

So the two valid forms would be:
1.) (how things work now)
<foreach ...>
<!-- stuff to do -->
</>
2.)
<foreach ...>
<in/>
<do>
<!--Stuff to do -->
</>
</>



What I would love to see is:


<fileset ID="foo" >
  <include ......
</fileset>

<attrib readOnly="false">
 <fileset ref="foo" />
</attrib>

<foreach ...type="FileSet" ref="foo">
       <do>
       <!--Stuff to do -->
       </>
</>

in addition to the more verbose sorts...
<foreach ...>
       <in>
         <fileset ref="foo" />
         <fileset>
            ....
         </fileset>
       </in>
       <do>
       <!--Stuff to do -->
       </>
</>

Fileset references are something ant had a long time ago and would really
reduce the size of my build files tremendously.



-------------------------------------------------------
This SF.net email is sponsored by: Tablet PC. Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for? http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers








-------------------------------------------------------
This SF.net email is sponsored by: Tablet PC. Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for? http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to