Return-Path: 
 <user-return-44011-apmail-ant-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-user-archive@www.apache.org
Received: (qmail 78454 invoked from network); 23 Jun 2004 12:35:06 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 23 Jun 2004 12:35:06 -0000
Received: (qmail 33476 invoked by uid 500); 23 Jun 2004 12:26:47 -0000
Delivered-To: apmail-ant-user-archive@ant.apache.org
Received: (qmail 32726 invoked by uid 500); 23 Jun 2004 12:26:33 -0000
Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:user-unsubscribe@ant.apache.org>
List-Subscribe: <mailto:user-subscribe@ant.apache.org>
List-Help: <mailto:user-help@ant.apache.org>
List-Post: <mailto:user@ant.apache.org>
List-Id: "Ant Users List" <user.ant.apache.org>
Reply-To: "Ant Users List" <user@ant.apache.org>
Delivered-To: mailing list user@ant.apache.org
Received: (qmail 32274 invoked by uid 99); 23 Jun 2004 12:26:24 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received: from [216.109.117.228] (HELO web60705.mail.yahoo.com)
 (216.109.117.228)
  by apache.org (qpsmtpd/0.27.1) with SMTP; Wed, 23 Jun 2004 05:26:23 -0700
Message-ID: <20040623122610.6175.qmail@web60705.mail.yahoo.com>
Received: from [68.237.85.107] by web60705.mail.yahoo.com via HTTP;
 Wed, 23 Jun 2004 05:26:10 PDT
Date: Wed, 23 Jun 2004 05:26:10 -0700 (PDT)
From: Xxx Yyy <ybobble-antmailinglist@yahoo.com>
Subject: Re: proper use of filesets...
To: Ant Users List <user@ant.apache.org>
In-Reply-To: <1087988276.79139.ezmlm@ant.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Although they look similar, they are very different in the files that
they include.  When you omit the <include/> or <exclude/> from a
fileset, it gets a default include/exclude list.

For example,
   <fileset dir="dir1"/>
could contain a file such as "dir1/test.txt".

When you specify <include/> that overrides the default list.
This fileset
   <fileset dir=".">
     <include name="dir1"/>
   </fileset>

cannot contain "dir1/test.txt".  It can contain, at most, "dir1".


This makes a difference in your example because delete will not delete
directories that are not empty.  The first fileset will delete the
directory "dir1" (assuming that it doesn't contain files in the exclude
list).  The second fileset will not delete "dir1" if it contains any
file.



--- EJ Ciramella <eciramella@upromise.com> wrote:
> What's the best way to use filesets (in tasks that
> support them)?
> 
> Delete, for example, you can use filesets two ways:
> 
>   <delete includeEmptyDirs="true">
>     <fileset dir="dir1"/>
>     <fileset dir="dir2"/>
>   </delete>
> 
> or 
> 
>   <delete includeEmptyDirs="true">
>     <fileset dir="${parent.dir}">
>      <include name="dir1"/>
>      <include name="dir2"/>
>     </fileset>
>   </delete>
> 
> I prefer the second example, but is there any
> benefit of one over the other?
> 
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org