DO NOT REPLY [Bug 18400] - add failonerror to target

2003-05-23 Thread bugzilla
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=18400.
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=18400

add failonerror to target

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WONTFIX



--- Additional Comments From [EMAIL PROTECTED]  2003-05-23 21:15 ---
jhuang: have you looked at the trycatch stuff in ant-contrib.sf.net? These
would seem to meet your needs in a cleaner, more structured manner.

I dont see any likelihood that targets will add failonerror; try/catch is a
better model as you can detect and act on failure, rather than just ignore it,


DO NOT REPLY [Bug 18400] - add failonerror to target

2003-04-10 Thread bugzilla
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=18400.
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=18400

add failonerror to target





--- Additional Comments From [EMAIL PROTECTED]  2003-04-10 12:47 ---
Maybe the try-Task of Ant-Contrib would help you.


DO NOT REPLY [Bug 18400] - add failonerror to target

2003-03-27 Thread bugzilla
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=18400.
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=18400

add failonerror to target





--- Additional Comments From [EMAIL PROTECTED]  2003-03-27 17:05 ---
What you are describing somewhat breaks the notion of dependancies as things
that the target depends on for proper functioning. 

Perhaps adding a failonerror to antcall would make more sense.

it might look something like this...

target name=report
  antcall target=t1 failonerror=false/
  antcall target=t2 failonerror=false/
  !-- do report type stuff here --
/target

Personally I think dependancies should be dependancies, though being able to
call a target such that it's failure is not fatal to the build might be useful
to support in some form.

I havn't used it, but I think the ant-contrib trycatch task might solve your
problem until some action is taken on this. Try this link:

http://ant-contrib.sourceforge.net/ant-contrib/manual/tasks/index.html