RE: [nant-dev] filesets and properties

[Lalonde, P. <pla...@ea...>]

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. =20

=20

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. =20

=20

That said, I'm pretty new to NAnt (but not to large build systems), and
would love to be re-educated on the issue.

=20

Paul

=20

-----Original Message-----
From: Scott Hernandez [mailto:sk...@eo...]=20
Sent: Wednesday, July 31, 2002 10:19 AM
To: Lalonde, Paul
Cc: nan...@li...
Subject: RE: [nant-dev] filesets and properties

=20

There was a discussion a ways back about supporting id/ref stuff for
elements (including filesets).=20

=20

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.

=20

I assume you want to reuse a fileset in multiple places. How do you feel
about the id/ref idea?

=20

It would look something like this.

=20

=20

                        <fileset id=3D"myfileset" basedir=3D"baz">

                                    <includes name=3D"**/*.cs"/>

                                    <excludes name=3D"foo.cs"/>

                        </ >

=20

                        <fileset ref=3D"myfileset"/> <!-would be the =
same
as embedding the above fileset-->

=20

You may want to look through the archives for more information. I think
there was a lengthy discussion (> 5 emails) about it.

=20

-----Original Message-----
From: nan...@li...
[mailto:nan...@li...] On Behalf Of
Lalonde, Paul
Sent: Wednesday, July 31, 2002 10:08 AM
To: 'nan...@li...'
Subject: [nant-dev] filesets and properties

=20

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:

=20

                        <property name=3D"myfileset" basedir=3D"baz">

                                    <includes name=3D"**/*.cs"/>

                                    <excludes name=3D"foo.cs"/>

                        </property>

=20

                        <echo message=3D"${myfileset}"/>

=20

would print (assuming my directory had foo.cs, bar.cs, qux.cs):

baz/bar.cs baz/qux.cs

=20

(it could resolve to full pathnames if that makes sense)

=20

Paul

=20