Return-Path: 
 <dev-return-79176-apmail-ant-dev-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-dev-archive@www.apache.org
Received: (qmail 19277 invoked from network); 14 May 2007 14:55:07 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 14 May 2007 14:55:07 -0000
Received: (qmail 88294 invoked by uid 500); 14 May 2007 14:55:12 -0000
Delivered-To: apmail-ant-dev-archive@ant.apache.org
Received: (qmail 88263 invoked by uid 500); 14 May 2007 14:55:12 -0000
Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@ant.apache.org>
List-Help: <mailto:dev-help@ant.apache.org>
List-Post: <mailto:dev@ant.apache.org>
List-Id: "Ant Developers List" <dev.ant.apache.org>
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Delivered-To: mailing list dev@ant.apache.org
Received: (qmail 88252 invoked by uid 99); 14 May 2007 14:55:12 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 May 2007 07:55:12 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Received: from [192.6.10.2] (HELO colossus.hpl.hp.com) (192.6.10.2)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 May 2007 07:55:05 -0700
Received: from localhost (localhost.localdomain [127.0.0.1])
	by colossus.hpl.hp.com (Postfix) with ESMTP id B39126B9C5
	for <dev@ant.apache.org>; Mon, 14 May 2007 15:54:43 +0100 (BST)
X-Virus-Scanned: amavisd-new at hplb.hpl.hp.com
Received: from colossus.hpl.hp.com ([127.0.0.1])
	by localhost (colossus.hpl.hp.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id SI0D9SA6XvnW for <dev@ant.apache.org>;
	Mon, 14 May 2007 15:54:42 +0100 (BST)
Received: from ha-node-br2.hpl.hp.com (ha-node-br2.hpl.hp.com [16.25.144.57])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by colossus.hpl.hp.com (Postfix) with ESMTP id 7DC7F6B9BD
	for <dev@ant.apache.org>; Mon, 14 May 2007 15:54:42 +0100 (BST)
Received: from [16.25.171.182] (chamonix.hpl.hp.com [16.25.171.182])
	by ha-node-br2.hpl.hp.com (8.14.1/8.13.4) with ESMTP id l4EEsQhS028916
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <dev@ant.apache.org>; Mon, 14 May 2007 15:54:26 +0100 (BST)
Message-ID: <46487822.7090901@apache.org>
Date: Mon, 14 May 2007 15:54:26 +0100
From: Steve Loughran <stevel@apache.org>
User-Agent: Thunderbird 1.5.0.10 (X11/20070221)
MIME-Version: 1.0
To: Ant Developers List <dev@ant.apache.org>
Subject: Re: Retry task container
References: <ab8e556c0705122132o383c10yae73b6975e5f5901@mail.gmail.com>
 <255d8d690705140649r6041f40cla68d34c4b0aa53ce@mail.gmail.com>
In-Reply-To: <255d8d690705140649r6041f40cla68d34c4b0aa53ce@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-HPL-MailScanner-Information: Please contact the ISP for more information
X-HPL-MailScanner: Found to be clean
X-HPL-MailScanner-From: stevel@apache.org
X-Virus-Checked: Checked by ClamAV on apache.org

Dominique Devienne wrote:
> On 5/12/07, Kevin Jackson <foamdino@gmail.com> wrote:
>> <retry noRetries="3">
> 
> noRetries as in "Number Of Retries" or "No retries"???
> 
> How about retrycount instead? --DD
> 
> PS: I second all comments made so far. <retry> could live in
> Ant-Contrib too, rather than Ant.
> 
> PPS: If <retry> had additionally a condition to satisfy before it
> executed its content, with Steve's internaltime attribute, it would
> have a lot of parallels with <waitfor>, no?
> 

ahh, you are into advanced workflows there. I am thinking of adding for 
smartforg a during component that deploys its children whenever a test 
is in a specific state, undeploys them when the state is not met, and 
redeploys them when the condition is met again. you could do the same 
with some while loops, and I will probably write the component through 
composition:

during extends During {

  condition extends NetworkVisible {
    host GmailJabberClient:host;
  }

   interval 1000;
   delay 5000;  //hysteresis effects

  action extends GmailJabberClient {
   user "host_account_1";
   password "secret";
  }


}

This would let me deploy things that go away when the external stuff 
they depend on (servers, the network itself) go away, but which return 
when the network comes back. I hate programs that complain or never 
recover from network outages.

And yes, we do use Gmail as an informal way of tracking the avaiability 
of remote machines. If my home servers arent listed as available, it 
means the network to the home is down. I think my next step would be to 
support shell commands to the server, which would be stunningly insecure 
but really cool.

-steve

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