ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Fetzer <elstonk...@yahoo.com>
Subject Re: onsuccess or onfailure
Date Fri, 10 Apr 2009 20:45:22 GMT
I don't get this Matt.  Can you fix the following to be what you're talking about:

<target name="main">
  <antcall target="target1"/>
  <antcall target="target2"/>
  <antcall target="target3"/>
  <antcall target="onsuccess"/>
  <antcall target="onfailure"/>
</target>

<target name="target1">
  <echo message="In target1"/>
</target>

<target name="target2">
  <echo message="In target2"/>
</target>

<target name="target3">
  <echo message="In target3"/>
</target>

<target name="onsuccess" unless="somehow I know all tasks were successful">
  <echo message="successful"/>
</target>



<target name="onfailure" unless="somehow I know something failed">
  <echo message="failure"/>
</target>


To me, I don't see any way to get to another target once it fails out of one.  The onsuccess,
yes, but not onfailure...

Thanks for having patience with me Matt!





________________________________
From: Matt Benson <gudnabrsam@yahoo.com>
To: Ant Users List <user@ant.apache.org>
Sent: Friday, April 10, 2009 9:19:44 AM
Subject: Re: onsuccess or onfailure


--- On Fri, 4/10/09, Eric Fetzer <elstonkers@yahoo.com> wrote:

> From: Eric Fetzer <elstonkers@yahoo.com>
> Subject: Re: onsuccess or onfailure
> To: "Ant Users List" <user@ant.apache.org>
> Date: Friday, April 10, 2009, 9:32 AM
> Sorry, I should have given you more
> detail.  It does exactly what it says.  When the build
> fails (i.e. a target that isn't set for onfailure="false"
> fails) or finishes with success, it immediately calls the
> target specified.  In my example, it would call either the
> onsuccess or onfailure targets.  Very useful to me because
> I want to send emails, unlock files in StarTeam, scan
> logs... for onfailure, but not for success.

In Ant you would ordinarily structure your target dependencies such that onsuccess and onfailure
were always part of the graph, but would use target if/unless attributes to en/disable them
at RT.  Alternately you might be able to write a custom target Executor to do something like
what NAnt does, but I wouldn't necessarily recommend that approach.

HTH,
Matt

> 
> 
> 
> 
> ________________________________
> From: Matt Benson <gudnabrsam@yahoo.com>
> To: Ant Users List <user@ant.apache.org>
> Sent: Thursday, April 9, 2009 4:24:12 PM
> Subject: Re: onsuccess or onfailure
> 
> 
> 
> 
> --- On Thu, 4/9/09, Eric Fetzer <elstonkers@yahoo.com>
> wrote:
> 
> > From: Eric Fetzer <elstonkers@yahoo.com>
> > Subject: onsuccess or onfailure
> > To: "Ant Users" <user@ant.apache.org>
> > Date: Thursday, April 9, 2009, 2:42 PM
> > Hi!  I'm an ex-NAnt user coming over
> > to the Ant side.  Most things are close to identical,
> but I
> > have a question about something I'm not finding.  In
> NAnt,
> > you can create properties:
> > 
> > <property name="nant.onsuccess"
> value="onsuccess"/> 
> > <property name="nant.onfailure"
> value="onfailure"/>
> > 
> > which will go to the corresponding onsuccess or
> onfailure
> > targets when finished based on whether it succeeded
> or
> > not.  I'm sure there is the equivalent in Ant, but
> have
> > been unable to find it.  Can someone please give me a
> link
> > or such?
> > 
> 
> This smells of some NAnt-ness quite foreign to Ant. 
> Personally speaking, I need more information about what
> these properties are supposed to do before I can offer any
> useful advice.
> 
> -Matt
> 
> > Thanks,
> > Eric
> > 
> > 
> >      
> 
> 
>      
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
> 
> 
>      


      

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


      
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message