> -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: Dienstag, 3. September 2002 10:22 > To: [EMAIL PROTECTED] > Subject: Re: [VOTE] Porting <fileset> 'file' attribute to 1.5 branch > > > On Tue, 3 Sep 2002, Knut Wannheden <[EMAIL PROTECTED]> wrote: > > From: Stefan Bodewig > >> > Wannheden, Knut wrote: > >> > > >> >> I was wondering what happens if the value identifies a > >> >> non-existant file. I suppose I will get a message like "No > >> >> directory specified for <fileset>.", right? > >> > >> I think so, as soon as you use it. > > > > In that case the error message is somewhat misleading. > > Well, yes. > > But whatever we do, we can not test for the files existance at fileset > definition time as it may be created during the build process. >
Yes, I understand that, but it shouldn't be hard to solve the problem anyway. Some checks in getDirectoryScanner(Project) would probably be enough, right? With a separate field for the file attribute you could also ensure that not both file and dir have been set. I could write a patch for this if you like. -- knut
