Bug 16123 - Failure with -logfile doesn't set exit value
Summary: Failure with -logfile doesn't set exit value
Status: RESOLVED FIXED
Alias: None
Product: Ant
Classification: Unclassified
Component: Core (show other bugs)
Version: 1.5.1
Hardware: Other other
: P3 normal (vote)
Target Milestone: 1.6
Assignee: Ant Notifications List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-15 17:51 UTC by Mike Castle
Modified: 2008-02-22 12:18 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Castle 2003-01-15 17:51:30 UTC
mcastle@dl-mcastle[09:40am]mrc/NWbuild/bin(1618) sh
/opt/app_home/ant/1.5.1/noarch/bin/ant -logfile ../logs/log.file
Cannot write on the specified log file. Make sure the path exists and you have
write permissions.
mcastle@dl-mcastle[09:41am]mrc/NWbuild/bin(1619) echo $?
0


Should set the exit code to 1 at least.

Actually, might not be a bad idea to audit all command line oriented failures
just to be paranoid.
Comment 1 Stefan Bodewig 2003-01-23 16:27:57 UTC
All command line problem should lead to a return code of 1 now.