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 31685] - [PATCH] typedef doen't fail with resource could not be found
Date Tue, 19 Oct 2004 14:49:19 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31685>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31685

[PATCH] typedef doen't fail with resource could not be found





------- Additional Comments From steve.morin@gmail.com  2004-10-19 14:49 -------
The latest patch basically addes unit tests for backward compatibility with 
the text as stated below.  It also perserves the current default and it's
behavior which is the setting of onerror="fail" adding onerror="failall" which
can be set to allow for failure under all error conditions including former
legacy nonfailure cases.  Failure (build exception) has been added to
resource="nonexistent.properties" for "failall".


>>  The default setting of the attribute was to specify the behaviour of
>>  <typedef>
>>  in ant 1.5.4 and earier - I called this "FAIL", but in ant 1.5.4, if one
>>  specified a
>>  resource or a file that did not exist, it will be reported but will not fail
>>  the build.

>>  The build would only fail if the build tried to make use of the type or
>>  task, in
>>  which case it would fail.

>>  As example of a build script not failing for a missing resource but
>>  reporting
>>  a warning is the check.xml build file that is in the ant cvs.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message