Return-Path: <tad1@cornell.edu>
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 43950 invoked from network); 29 Jun 2000 13:35:11 -0000
Received: from postoffice2.mail.cornell.edu (132.236.56.10)
  by locus.apache.org with SMTP; 29 Jun 2000 13:35:11 -0000
Received: from pyro (pyro.cit.cornell.edu [128.253.57.45])
	by postoffice2.mail.cornell.edu (8.9.3/8.9.3) with SMTP id JAA07993
	for <ant-dev@jakarta.apache.org>; Thu, 29 Jun 2000 09:35:05 -0400 (EDT)
Message-Id: <3.0.2.32.20000629093508.013b2660@postoffice2.mail.cornell.edu>
X-Sender: tad1@postoffice2.mail.cornell.edu
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) -- [Cornell Modified]
Date: Thu, 29 Jun 2000 09:35:08 -0400
To: ant-dev@jakarta.apache.org
From: Tom Dimock <tad1@cornell.edu>
Subject: Re: Core Task spec 0.1
In-Reply-To: <m3r99giuqk.fsf@sbodewig.bost.de>
References: <Mark Brouwer's message of "Thu, 29 Jun 2000 11:43:13 +0200">
 <4.3.2.7.2.20000628213711.00b29aa0@pop.planet.nl>
 <395B1A31.B1C7F5E1@virgil.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

At 01:37 PM 06/29/2000 +0200, Stefan wrote:
>>>>>> "MB" == Mark Brouwer <mark.brouwer@virgil.nl> writes:
>
> MB> <!ELEMENT patternset (include*, exclude*)> 
> MB> <!ATTLIST patternset id ID #REQUIRED>
>
>This sounds useful to me. I'd like to see this and filesets and maybe
>others merged with a better properties mechanism.

Hear, hear.  I like the filesets, but would like to have named filesets:

<fileset name="myfiles" dir="dofussdir">
  <include name="**/*.doofuss"/>
</fileset>

Then the fileset could be specified as a source:

<copy src.fileset="myfiles" dest.dir="dofussdir"/>

Note also my use of the dot in the attribute names - I think this would
make the documentation clearer.  The source would be src.file or src.dir or
src.fileset, with one src specification being required.  Same with the dest
- dest.file or dest. dir with one dest specification being required.  Being
able to use named filesets accomplishes two goals.  It allows multiple
tasks to be run against the same set of files without having to respecify
the fileset, and it would allow more general use of filesets in tasks where
there may be more than one fileset in use - <exec> being a fine example....

> MB> Also the concept of having attributes for pattern matching and
> MB> elements in your fileset is overkill IMHO, before you know it you
> MB> have shortcuts everywhere.
>
>It's more the "for backward compatibility/historical reasons" kind of
>thing than to provide shortcuts.

Put them in those reasons, but mark them as deprecated?
----------------------------------------------------------------------------
       Tom Dimock  ----  Cornell University  ----  tad1@cornell.edu
"There go my people.  I must follow them, for I am their leader."  M. Gandhi