You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2002/08/01 09:39:06 UTC
DO NOT REPLY [Bug 11270] -
FileSet and DirSet break if the directory does not exist
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11270>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11270
FileSet and DirSet break if the directory does not exist
------- Additional Comments From cote@computer.org 2002-08-01 07:39 -------
Regarding comments of Jose Alberto Fernandez
If I got the following task
<uptodate property="toto.notRequired">
<srcfiles refid="toto.class.fileset"/>
<srcfiles refid="toto.otherfiles.fileset"/>
<mapper type="merge" to="${toto.dir}/ejb-jar.xml"/>
</uptodate>
Suppose the fileset toto.class.fileset point to a inexisting directory just
after a clean. And that some file in toto.otherfiles.fileset always exist. If
they are uptodate regarding ejb-jar.xml, the task will conclude that the file
are uptodate. The behavior I would like would be to that task with inexisting
fileset are never uptodate.
I think fileset for directory that doesn't exist should always throws a error
when used from task like compile. It's only when called from task like uptodate
that it is acceptable. I think what we need is different behavior when the
fileset is called from different task, not a attribute that modify the behavior
for all task.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>