Another hack is to explicitly exclude certain tests by modifying your
local project.xml file to add an excludes filter to the build...
<unitTest>
<includes>
<include>**/*Test.java</include>
</includes>
<excludes>
<exclude>**/Foo*Test.java</exclude>
</excludes>
...
On Friday, August 29, 2003, at 07:11 am, Kristian Koehler wrote:
Hi Siva, Hi Alex
of course this is a possible workaround (this is what we are doing
right now), but on the other hand why skip all working tests just
because one single test fails while attempting to connect via HTTP?
It just doesn't seem like the right thing to do IMHO.
So why not change the test to run everywhere out of the box?
Steffen and Kristian
Siva wrote:
A more easier approach which i follow is setting
one of the following maven properties via -D flag
maven.test.skip=true
or
maven.test.failure.ignore
Siva
----- Original Message ----- From: "Alex Blewitt"
<[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 28, 2003 9:47 PM
Subject: Re: DownloadTest Failure when working offline/ behind
firewall
I really think that there should be a split between 'build' and
'test'.
Whilst it may be desirable for both to occur by default, it would be
incredibly useful to be able to build w/o testing. I've found that
the easiest way to disable all tests is to comment the
etc/project.xml file and commenting (using <!-- -->) out the
unitTestDir element ...
That way, you should be able to build w/o testing.
Alex.
James
-------
http://radio.weblogs.com/0112098/
