Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
From: glennm@ca.ibm.com
Importance: Normal
Subject: Re: <copy> doesn't say when it can't find the file
To: ant-dev@jakarta.apache.org
Message-ID: <OF4444E8A3.C8733923-ON85256981.004B71E9@torolab.ibm.com>
Date: Mon, 23 Oct 2000 09:45:49 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii


I'll see what I can do once the release goes out, Diane.  There are a
number of little fixes I'd like to do, but as this isn't a critical issue
its going to have to wait.  And I'll address the "file" vs. "files"
messages too. :-)

Glenn McAllister
Software Developer. IBM Toronto Lab, (416) 448-3805
"An approximate answer to the right question is better than the
right answer to the wrong question." - John W. Tukey


Please respond to ant-dev@jakarta.apache.org

To:   ant-dev@jakarta.apache.org
cc:
Subject:  <copy> doesn't say when it can't find the file

If you ask <copy> to copy a file that doesn't exist, it silently does
nothing. I would prefer having it say it couldn't find the file.
Currently, <delete> tells you that:

Buildfile: test.xml
bogusdelete:
   [delete] Could not find file D:\dianeh\src\main\bogus to delete.

but I actually don't care if it couldn't find the file, since it's just
deleting it anyway (think 'rm -f foo'). On the other hand, I do care if it
can't find a file I've asked to be copied. The way it is now, the output
looks the same if it can't find the file to copy as it does when the copy
doesn't happen simply because the source-file is up-to-date with the
target-file (ie., the only logging output is just the target name), which
is pretty misleading.

Thanks,
Diane


=====
(holtdl@yahoo.com)


__________________________________________________
Do You Yahoo!?
Yahoo! Messenger - Talk while you surf!  It's FREE.
http://im.yahoo.com/