ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scot P. Floess" <>
Subject Re: Problem converting path to property when a fileset's dir does not exist
Date Thu, 20 Oct 2005 14:29:16 GMT

Thanks for the reply.  I followed the links and sure enough there is 
mention of this issue.  I incorrectly referred to when, in 
fact, the class I had been looking at was (as seen 
in the link you provided).

 From what I gather it looks like in 1.7 I can use something called 
<files> (I think its new).  I'll just wait until 1.7 and worry about 
this issue then.  Its really not a "show stopper" for me...more of an 
annoyance but tolerable :D

Thanks for the reply....

Dominique Devienne wrote:

>On 10/19/05, Scot P. Floess <> wrote:
>>I'm not sure why the source behind is coded to raise and
>>exception if the directory is not there...or more to the point why I
>>can't simply specify to <path> something like "ignore-non-existants"
><path> does ignore non-existent files, but the <fileset> within
>*requires* it's dir attribute to be a valid directory. <path> is
>basically asking <fileset> for the files it selects, and fileset
>complains that it's 'base' directory doesn't exists. I think there's a
>BugZilla request to add an attribute to stop <fileset> from
>complaining when its dir. See
> --DD

Scot P. Floess
27 Lake Royale
Louisburg, NC  27549

252-478-8087      (home)
919-319-1099 x117 (work)

Chief Architect JPlate
Chief Architect JavaPIM

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message