Mariano Benitez wrote:
it is VERY java oriented to use try/catch to implement this, and I
would rather use the way it is implemented in the rest of the ant
tasks, like javadoc, junit, etc.
it is very simple also to change the value of haltonerror to
true/false, instead of ignoring a catch.
Although I evaluated the try/catch solution, I still want this feature
to be included.
Anyway, is there any philosophical objection why this should not be
included, does it go against some rule? just curious...
MAriano
Jose Alberto Fernandez wrote:
This can be achieved with the <trycatch/> task from antcontrib.
Take a look at it.
I think it is becoming time for some of this very useful and
generic tasks to make its way into CORE.
What do people think? What antcontrib people think?
Jose Alberto
-----Original Message-----
From: Mariano Benitez [mailto:[EMAIL PROTECTED]
Sent: 11 June 2003 00:35
To: Ant Developers List
Subject: Re: adding success & failure to <subant>
I completely desire that, for long nested builds for
regression testing
makes life really easy to just send a build to run, and if fails, no
problem, keep going to the next build.
MAriano
Steve Loughran wrote:
I think I posted this last week, but it got lost
1. What do people think about adding the ability to set
properties if
a subant or ant call failed/succeeded. This lets me do
complex things
in cruise control.
2. How best to do it?
Here is one example implementation
<subant antfile="driver/" target="build"
succeeded="driver.built" failoneerror="false"/>
<target name="test-driver" depends="driver"if="driver.built" >
<subant antfile="driver/" target="test"
succeeded="driver.tested" failoneerror="false"/>
</target>
<target name="app" depends="driver" if="driver.built" >
<subant antfile="app/" succeeded="app.built"
failoneerror="false"/>
</target>
<target name="test-app" depends="app" if="app.built" >
<subant antfile="app/" succeeded="app.built"
failoneerror="false"/>
</target>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
