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 2004/01/12 22:07:18 UTC
DO NOT REPLY [Bug 26073] New: -
Abort task or generalization of fail task
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=26073>.
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=26073
Abort task or generalization of fail task
Summary: Abort task or generalization of fail task
Product: Ant
Version: 1.6.0
Platform: Other
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: Other
Component: Core tasks
AssignedTo: dev@ant.apache.org
ReportedBy: brian.bray@theradoc.com
A new abort task, or an enhancement to the fail task, that would allow you to
quit in the middle of a project but still return successfully would be very nice
and doesnt seem too hard.
I have a fetch target that, if nothing has changed since the last build does a
fail with a "build not needed" message. The master build file has to
"catch/trap" this error using a <subant> task. But the output is messy and it
would be a lot cleaner if there were just an abort task.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org