Yes the exit code is != 0, so the command should fail.
I'm sure i'm doing something wrong here, i'll keep looking for my mistake
thanxs for your help,
Max
On 2012-04-05, Maxime CARPENTIER wrote:
> yes sorry i forgot to mention the failonerror attribute is set to true
but
> it still doesn't fai
On 2012-04-05, Maxime CARPENTIER wrote:
> yes sorry i forgot to mention the failonerror attribute is set to true but
> it still doesn't fail
Well, it's been quite some time since I last used CVS, so I'm not sure
about the details and don't have any CVS repo around to test.
Ant will fail if "cvs
Hi Stefan,
yes sorry i forgot to mention the failonerror attribute is set to true but
it still doesn't fail
Max
On 2012-04-05, Maxime CARPENTIER wrote:
> this command works well except for one thing : it doesn't fail if
someone
> else changes and commit files i want to commit just before th
On 2012-04-05, Maxime CARPENTIER wrote:
> this command works well except for one thing : it doesn't fail if someone
> else changes and commit files i want to commit just before the command
> commit :
[snip]
> Only a "commit aborted" message shows off, but the build stays
> successful...
Does it
Hello list,
i'm having trouble using the cvs commit command via ant :
this command works well except for one thing : it doesn't fail if someone
else changes and commit files i want to commit just before the command
commit :
[cvs] cvs commit: Examining .
[cvs] cvs commit: Up-to-d
If only i had listened :) Thank you for your help all working perfectly.
On 24 Nov 2009, at 19:49, Greg Roodt wrote:
batchtest
-
To unsubscribe, e-mail: user-unsubscr...@ant.apache.org
For additional commands, e-mail: user-
Ready to try my suggestion?
Have you tried setting the failure properties on "batchtest" rather
than the "junit" task?
On Tue, Nov 24, 2009 at 7:47 PM, Ben Cuthbert wrote:
> I see. And yes it is firing them now. But I am back to the old problem that
> the build does not fail when there is an e
I see. And yes it is firing them now. But I am back to the old problem
that the build does not fail when there is an error
Ant has resolved your variables references.
Your "if" should look like this:
On Tue, Nov 24, 2009 at 7:32 PM, Ben Cuthbert wrote:
> Yes I got the following error running in debug
>
> test-unit:
> Skipped because property 'true' not set.
>
>
> ant build -Dunit.test=true -verbose
>
> What is th
Yes I got the following error running in debug
test-unit:
Skipped because property 'true' not set.
ant build -Dunit.test=true -verbose
What is the property true
On 24 Nov 2009, at 14:42, glenn opdycke-hansen wrote:
Suggest that you run in verbose mode. i suspect that the target
could be
Suggest that you run in verbose mode. i suspect that the target could be
the cause.
-glenn
Strange if i put in the changes as you suggested it does not even execute my
targets. If I run the following on the command line
ant build -Dunit.test=true
On Monday, November 23, 2009, at 09:52PM, "glenn opdycke-hansen"
wrote:
>I agree that there is nothing obviously incorrect. However, do
I agree that there is nothing obviously incorrect. However, do you run unit
tests and acceptance tests at the same time?
If so then there is a potential problem that the script will run the unit
tests then the acceptance tests then check the properties.
I suggest that the not be used, instead hav
I cant see anything obviously wrong there, but my test targets are
normally a bit simpler.
Have you tried setting the failure properties on "batchtest" rather
than the "junit" task? Something weird may be happening because you
are forking in "batchtest".
On Mon, Nov 23, 2009 at 6:43 PM, Ben Cuth
Here it is
haltonfailure="no" haltonerror="no"
failureproperty="tests.failures" errorproperty="tests.errors"
Could you please paste the entire Ant "test" target you are using?
You would definitely need to be checking for the error property, since
its not a test failure, thats an error.
On Sat, Nov 21, 2009 at 6:25 PM, Ben Cuthbert wrote:
> What I have is the the following
>
> haltonfailure="no" h
What I have is the the following
haltonfailure="no" haltonerror="no"
failureproperty="tests.failures" errorproperty="tests.errors"
>
On 21 Nov 2009, at 18:20, glenn opdycke-
it appears that the name of the property being set is different than what is
being checked:
On Sat, Nov 21, 2009 at 12:12, Ben Cuthbert wrote:
> Strange thing is, if I set this property in the top of the file
>
>
>
> And then in my target put
>
>
>
> I get and error
>
> build-common.xml:347:
Strange thing is, if I set this property in the top of the file
And then in my target put
I get and error
build-common.xml:347: Test failed!!!
On 21 Nov 2009, at 16:33, Ben Cuthbert wrote:
Yes so I have the following line in the same target at the end, I
see the unit test error but th
I set those and nothing, still unit test fails but the build passes.
In the verbose log I just see
[junit] 'filtertrace=true'
[junit] 'haltOnError=false'
[junit] 'haltOnFailure=false'
[junit] 'showoutput=false'
[junit]
'formatter
=org.apache.tools.ant.taskdefs.optional.jun
What if you change the halton* to "no" ?
I would run it with verbose set on in order to get more details.
--glenn
On Sat, Nov 21, 2009 at 02:43, Ben Cuthbert wrote:
> failureproperty="tests.failures" errorproperty="tests.errors">
>
Strange thing is, if I set this property in the top of the file
And then in my target put
I get and error
build-common.xml:347: Test failed!!!
On 21 Nov 2009, at 16:33, Ben Cuthbert wrote:
Yes so I have the following line in the same target at the end, I
see the unit test error but th
Yes so I have the following line in the same target at the end, I see
the unit test error but the build does not stop
On 21 Nov 2009, at 10:05, Greg Roodt wrote:
Are you picking up your tests.failures property somewhere to fail the build?
e.g.
On Sat, Nov 21, 2009 at 8:43 AM, Ben Cuthbert wrote:
> When one of my unit tests fail the build is still successful. But in my ant
> config I have the following
>
> failureproperty="tests.failures" errorpropert
When one of my unit tests fail the build is still successful. But in
my ant config I have the following
failureproperty="tests.failures" errorproperty="tests.errors">
Please do not use the Ant user mailing
list for personal correspondence.
Jeffrey E. (Jeff) Care
[EMAIL PROTECTED]
IBM WebSphere Application
Server Development
WAS Pyxis Lead
Release Engineer
Hi Venkatesh
I have a friend called Venkatesh babu and he is from bangalore. Just wondering
if you were the person I know
Venkatesh Babu <[EMAIL PROTECTED]> wrote: Hello All,
I'm calling an ant target from within my batch script
as follows:
cmd/C ant -f mailer.xml sendmail
My problem is that i
Hello All,
I'm calling an ant target from within my batch script
as follows:
cmd/C ant -f mailer.xml sendmail
My problem is that if the sendmail target fails, I
have to stop execution of my batch script. For that I
tried adding the following statement after the ant
call:
if %ERRORLEVEL% != 0 go
Try :
./bootstrap.sh
./build.sh install-lite
you are probably hit by remnants of older versions of ant in the
bootstrap dir.
Cheers,
Antoine
Hugh Field-Richards wrote:
Hi
I am upgrading from 1.5.3 and am having a few problems. I get the
following failure when I try to build the 1.6.1 source o
Hi
I am upgrading from 1.5.3 and am having a few problems. I get the
following failure when I try to build the 1.6.1 source on a Dual G5
running OS X 10.3.2.
apache-ant-1.6.1 > ./build.sh install-lite
... Bootstrapping Ant Distribution
... Compiling Ant Classes
Note: Some input files use or overri
30 matches
Mail list logo
