|
I didn’t drop enough information into my mail. I’m proposing that a representation for a fileset could be a space-delimited collection of filenames in a property.
My only difficulty with the id/ref idea relates to adding a new class of object, the fileset, where an existing object, the property, could likely do the job.
That said, I’m pretty new to NAnt (but not to large build systems), and would love to be re-educated on the issue.
Paul
-----Original Message-----
There was a discussion a ways back about supporting id/ref stuff for elements (including filesets).
I’m not sure how properties would work for this. Right now there isn’t really support for any type of property other than a string; and in-fact, the property add methods takes a string key and value.
I assume you want to reuse a fileset in multiple places. How do you feel about the id/ref idea?
It would look something like this.
<fileset id="myfileset" basedir="baz"> <includes name="**/*.cs"/> <excludes name="foo.cs"/> </ >
<fileset ref=”myfileset”/> <!—would be the same as embedding the above fileset-->
You may want to look through the archives for more information. I think there was a lengthy discussion (> 5 emails) about it.
-----Original Message-----
I was mucking around with Nant, and found myself needing a persistent fileset, and was thinking about a syntax that merges the idea with a property. How do people feel about:
<property name="myfileset" basedir="baz"> <includes name="**/*.cs"/> <excludes name="foo.cs"/> </property>
<echo message="${myfileset}"/>
would print (assuming my directory had foo.cs, bar.cs, qux.cs): baz/bar.cs baz/qux.cs
(it could resolve to full pathnames if that makes sense)
Paul
|
- [nant-dev] filesets and properties Lalonde, Paul
- RE: [nant-dev] filesets and properties Scott Hernandez
- RE: [nant-dev] filesets and properties Lalonde, Paul
- RE: [nant-dev] filesets and properties Smith, Eric V.
