Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@apache.org Received: (qmail 38795 invoked from network); 6 Apr 2002 03:31:59 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 6 Apr 2002 03:31:59 -0000 Received: (qmail 24208 invoked by uid 97); 6 Apr 2002 03:32:00 -0000 Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org Received: (qmail 24192 invoked by uid 97); 6 Apr 2002 03:32:00 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 24181 invoked from network); 6 Apr 2002 03:32:00 -0000 Message-ID: <06ea01c1dd1b$9a9dc190$6501a8c0@darden.virginia.edu> From: "Erik Hatcher" To: "Ant Users List" References: <20020406025611.44685.qmail@web13407.mail.yahoo.com> Subject: Re: javac and fileset Date: Fri, 5 Apr 2002 22:31:56 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "Diane Holt" To: "Ant Users List" Sent: Friday, April 05, 2002 9:56 PM Subject: Re: javac and fileset > --- Erik Hatcher wrote: > > Both are very much "path-like" (why the "like"?) structures. Neither > > are equivalent to the dir attribute of . > > >From the page: > This task forms an implicit FileSet and supports all attributes of > (dir becomes srcdir) > > > Sure, you can specify a dir, but also two, three, or more directories > > also. > > srcdir="path1;path2;path3" > > Right -- that was my example in my previous post (except I only had two :) > > > > > > > > > > > But you can't use a , because (and 'srcdir') only accepts > directories, and only returns files. Now that there's a > , you should be able to use that -- but, since the original poster > was trying to reuse a set of files, that's not really going to do what he > was looking to do (nothing using or 'srcdir' would, as far as I can > see anyway). As always, you're right! (except that they are still path-like structures internally). I just stared at the code for a bit and set up an example (that I should have done before speaking the first time :) that of course failed when I tried a nested . It actually seems silly that it won't work with files there, since you can of course use includes/excludes to pick and choose files how you want. I don't think it would be a tough modification to have it allow files there though. Things like this are fishy -when a task supports a Path, yet doesn't support it fully. I'm sure we have other such weirdnesses like this though. Erik -- To unsubscribe, e-mail: For additional commands, e-mail: