Bug 39798 - Verbose attribute in delete task not working
Summary: Verbose attribute in delete task not working
Status: RESOLVED INVALID
Alias: None
Product: Ant
Classification: Unclassified
Component: Core tasks (show other bugs)
Version: 1.6.5
Hardware: PC Windows 2000
: P2 normal (vote)
Target Milestone: ---
Assignee: Ant Notifications List
URL:
Keywords: JDK1.4
Depends on:
Blocks:
 
Reported: 2006-06-13 10:04 UTC by David Corley
Modified: 2008-02-22 12:18 UTC (History)
0 users



Attachments
Self-contained example of the delete task verbose problem (836.67 KB, application/zip)
2006-06-30 09:06 UTC, David Corley
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Corley 2006-06-13 10:04:53 UTC
I'm using the delete task to remove a large number of file/directories, and I
don't want my log file listing everything that's being deleted. However, when I
set the verbose attribute of the delete task to false, the files being deleted
are still being listed. I've tried entering both "false" and "no", but the
result is always the same. I'm using Ant 1.6.5 with jdk1.4.2_10 on a Win 2k box.
Comment 1 Matt Benson 2006-06-27 20:59:43 UTC
I can't reproduce the behavior you describe.  Please attach a self-contained
example to evoke this problem.
Comment 2 David Corley 2006-06-30 09:06:05 UTC
Created attachment 18548 [details]
Self-contained example of the delete task verbose problem

There's an included .bat file that has been renamed to .txt to avoid being
stripped by virus-scanners. You may need to edit it to point to your ant home.
Comment 3 David Corley 2006-06-30 09:08:24 UTC
OK, 
Sorry it took so long to get back. I've attached a self-contained example with a
batch file to get you up and running...just rename the .txt file in the
"delete-issue" directory to .bat, and edit it to point to your ant home
You may also need to edit the build.xml to point to wherever you unzipped the
zip file to, if you didn't unzip it directly to c:\
Comment 4 Matt Benson 2006-06-30 15:11:34 UTC
Here is the output I get:

Buildfile: build.xml
     [copy] Copying 390 files to C:\work\delete-issue\for-deletion

clean:
   [delete] Deleting 390 files from C:\work\delete-issue\for-deletion
   [delete] Deleted 36 directories from C:\work\delete-issue\for-deletion

BUILD SUCCESSFUL
Total time: 6 seconds

This looks normal to me... what do you get?
Comment 5 David Corley 2006-07-01 19:52:54 UTC
That's what I would expect to see, but I get a full listing. Would it be
possible for you to verify it using the same setup I have? JDK1.4.2_10, Ant
1.6.5, Win2k?
Comment 6 Peter Reilly 2006-10-31 03:04:02 UTC
I have tried with jdk1.4.2_12 on a win 2k box with ant 1.6.5
and do not see the problem.
Comment 7 Matt Benson 2006-10-31 06:40:31 UTC
well, duh.  Peter, did you run the build with plain Ant or with the included
batch file?  The batch file passes "-verbose" to Ant, which causes the huge
listing.  I'm not sure why you're using this custom batch file to launch Ant
anyway.  You should probably join the userlist to get a better idea of how to
configure your system without having to resort to such things.  Especially,
forgive me for saying, when they waste others' time looking for problems that
are not there.  :)
Comment 8 Peter Reilly 2006-10-31 06:53:08 UTC
Opps, you are right, I did not see the -verbose
in the included bat file, 
I did not use the included bat file as the java and ant dirs
are hard-coded.
Do not be too hard on reporters of bugs, it is important to
get reports on user experiances with ant.
Comment 9 Matt Benson 2006-10-31 07:03:32 UTC
(In reply to comment #8)
> Do not be too hard on reporters of bugs, it is important to
> get reports on user experiances with ant.

Hell, I smiled, didn't I? >:)