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 19077] New: - Telnet task doesn't support failure
Date Wed, 16 Apr 2003 16:21:32 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=19077>.
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=19077

Telnet task doesn't support failure

           Summary: Telnet task doesn't support failure
           Product: Ant
           Version: 1.6Alpha (nightly)
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Optional Tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: apache@eskimoman.net


The Ant telnet task doesn't support failing early if something goes wrong. What 
I wanted to do was run a script on a remote server, which finishes with "ok" if 
everything worked and "failed" if not. The remote script could take some time, 
which is why waiting for "ok" with a timeout wasn't quite good enough.

I've added code to TelnetTask which allows a new "failon" attribute for <read> 
elements. If the text in the attribute is read from the connection, the task 
fails. I use this to stop a build if deployment to a remote container fails.

I'll attach the patch (cvs -q diff -u) after creating the bug.

Mime
View raw message