I'm quite late to this party, but bear in mind Ant 1.7 also includes a <files> collection which has no basedir whatsoever if you ever need to combine files from various volumes.
HTH, Matt --- On Sun, 5/3/09, Patrik Nagel <[email protected]> wrote: > From: Patrik Nagel <[email protected]> > Subject: Re: fileset based on paths in file > To: "David Weintraub" <[email protected]>, "Ant Users List" > <[email protected]> > Date: Sunday, May 3, 2009, 12:39 PM > It's for a fileset. I tried the > "includesfile" attribute from the > fileset task. It does exactly what I'm looking for! > > Tanks a lot! > Patrik > > David Weintraub wrote: > > Is this for a path or a fileset? There's a big > difference. A path is > > simply a collection of directories while a fileset > selects files in a > > directory. > > > > If this is for a path, you could use a properties file > and separate > > those directories via a colon or semicolon. > > > > If this is a fileset, you can try using the > "includefile" attribute. > > For example: > > > > <fileset dir="/" > > > includefile="${my.include.file}/> > > > > And the include file will look like this: > > > > home/dev/src/reporting/** > > home/dev/src/common/** > > home/testing/src/logger/** > > > > On Sat, May 2, 2009 at 2:46 PM, Patrik Nagel <[email protected]> > wrote: > > > >> Hi, > >> > >> I would like to create a fileset based on paths > which have no base directory > >> in common. Additionally, the paths are stored in a > text file. > >> > >> Such a text file might looks as follows: > >> /home/dev/src/reporting > >> /home/dev/src/common > >> /home/testing/src/logger > >> > >> Is there a way to read the paths from the text > file and "add" them to a > >> fileset? Within this fileset I would apply a > filename selector to collect > >> all build.xml files. Note that the fileset is used > as a child within an > >> ivy:buildlist task. > >> > >> Any help would be appreciated! > >> > >> Regards, > >> Patrik > >> > >> > --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > >> > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
