Hi all,
After multiple iterations and failed Hudson build, Mike and me got it
running:
We upgraded the build.xml and Hudson configuration to use now Clover 2.6.3
with a new license for Apache projects granted by Nick Pellow from
Atlassian. The new reports now cover all tests not only the
Uwe, do you know why the assert lines come through as not covered?
Are we not running w/ asserts enabled when we run with clover?
Mike
On Thu, Dec 17, 2009 at 1:25 PM, Uwe Schindler u...@thetaphi.de wrote:
Hi all,
After multiple iterations and failed Hudson build, Mike and me got it
running:
I will try this out later and add an always-failing assert to the code and
try with/without clover. I will add this as a test:
try {
assert false;
fail(asserts disabled)
} catch (AssertionFailedError e} {}
Maybe Nick can explain this to us. This was the same behaviour in clover