You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ant.apache.org by Daisy Guo <da...@sitraka.com> on 2002/12/13 21:13:48 UTC
Could not set ErrorsBeginAt attribute in Condition's Http element
I checked the documentation, it said ErrorsBeginAt is supported, but ant
(1.5.1) complains:
file:D:/shared/rmitest/tool.xml:408: Class
org.apache.tools.ant.taskdefs.condition.Http doesn't support the
"errorsbeginat" attribute.
Does anybody ever successfully used this?
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Could not set ErrorsBeginAt attribute in Condition's Http element
Posted by Steve Loughran <st...@iseran.com>.
----- Original Message -----
From: "Daisy Guo" <da...@sitraka.com>
To: "Ant Users List" <an...@jakarta.apache.org>
Sent: Friday, December 13, 2002 12:13
Subject: Could not set ErrorsBeginAt attribute in Condition's Http element
> I checked the documentation, it said ErrorsBeginAt is supported, but ant
> (1.5.1) complains:
>
> file:D:/shared/rmitest/tool.xml:408: Class
> org.apache.tools.ant.taskdefs.condition.Http doesn't support the
> "errorsbeginat" attribute.
>
> Does anybody ever successfully used this?
ahh, that is fixed in the ant1.6 and 1.5.2 branches in CVS, someone (me),
got the case wrong for the method, it is SetErrorsBeginAt(int value) rather
than setErrorsBeginAt(), so Ant wont set that attribute
If you get an updated version from CVS it works (or correct your own copy).
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>