really - Are you sure that works ? the fileset takes a refid attribute that you use to reference a defined fileset like :The Fine Manual says, "File Sets can appear inside tasks that support this feature or at the project level, i.e., as children of project." But I had trouble figuring out how to use the children of project feature... to keep as much of the build script to cut-paste-and-pray as possible. What I wanted to do was:
<csc output="${builddir}bin\${assemblyname}" target="library" debug="${debug}"> <references basedir="${referencedir}" fileset="References" /> <sources basedir="${builddir}" fileset="Sources" /> <resources basedir="${builddir}" fileset="Resources" /> </csc>
And I'm happy to report that I can! But the ID attribute of the fileset was the undocumented bit.
<fileset id="References"> <includes asis="true" name="System.dll"/> ... <includes name="Xolutions.Data.Sql.dll"/> </fileset>
<csc output="${builddir}bin\${assemblyname}" target="library"
debug="${debug}">
<references refid="references"/>
...
</csc>and you'd do exactly the same thing with the copy task. Sounds like we need to document that a bit better and add some examples of named filest usage.
and neither does any othe task. Filesets are nested child elements of <csc> etc as described above.However, the copy task no workie like the csc task. :( Kind of a kink in the usefulness. I would've expected this to do the trick:
<copy todir="${integrationdir}\bin" basedir="${referencedir}" fileset="References" />
(And maybe whine a little bit that COPY and VSSGET doesn't support a filesets attribute, yet. :)
depends on what part. the task doc is autogenerated from code comments and soon datatype doc will be also. Anything else is just html and you can feel free to submit patches to this list.<blantant_newbie_whining> The NAnt website documentation could use some freshening... Has anybody considering adding a column to the Task page (and attributes) that indicates which version first supports the feature? Might reduce the number of different sets of dox and certainly my confoundedness.
Since I hate whiners, how does one go about volunteering to splotch in
some new documentation patches? I'm also putting together a Textpad
syntax file and Visual Studio schema (to support tag autocompletion) if
anybody's interested.
the nantcontrib poject is there for the tasks that for whatever reason do not make it into the main nant codebase. We are woking to make sure the the nantcontrib binaries are always released in sync with nant releases.While you're at it, would somebody please kill the nantcontrib project at SF? The fact that it's out there and can be found is likely to cause people like me to continue to hurt themselves... :) I wasted more time trying to get cvs and nantcontrib to work than I did just commenting out the mainline NAnt RC2 unit tests that don't work for some reason and just using the RC2 version.
Ian
------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
