ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18400] - add failonerror to target
Date Thu, 27 Mar 2003 17:05:24 GMT
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 gus.heck@olin.edu  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

Mime
View raw message