But be warned it will be horribly slow, since will scan all files on all file-systems mounted on /... <fileset> alway scans everything, even if all its includes do no contain any regex, which IMHO is a deficiency (i.e. an missing optimization).
I can see two optimizations fileset *should* have: 1) <fileset dir="somedir" includes="somesubdir/**" /> Do not start scanning all files at somedir, but somedir/somesubdir. 2) <fileset dir="somedir" includes="somesubdir1/A, somesubdir2/B" /> Do not start scanning all files at somedir, and do not scan at all for that matter, but look over all those 'fully defined' (i.e. no regex) included files, and add to the fileset the ones that exists. These two optimizations would significantly speed up tasks using these kind of fileset definitions. If I had to pick between the two, I guess (2) is the most common case. --DD PS: Note also that a recent but report on Javadoc in Ant being significantly slower than javadoc command line when specifying explicitly the classes to operate on would be taken care of often by (1) and (2). -----Original Message----- From: tek1 [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 12:30 AM To: Ant Users List Subject: Re: pulling .jars from a path? hi stefan. i will give your suggestion a try. thanks. At 09:42 03/01/15 +0100, you wrote: >On Tue, 14 Jan 2003, <[EMAIL PROTECTED]> wrote: > > > is it possible to pull all the .jars listed in a path as a fileset > > (for inclusion in the "lib" nested element of the "war" task)? > ><fileset>s in Ant (currently) have to be rooted in a common base >directory. This is generally not true for an arbitrary collection of >files, at least on OSes with multiple file system roots (read >drives). > >If you are on a system with a single file system root - assuming "/" >for the rest here - you could (1) <pathconvert> your path to a comma >separated list and (2) use that as the includes attribute in a ><fileset> with dir="/". > >Stefan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
