On Thu, 2003-12-04 at 04:04, Vincent Massol wrote:
> > No problem, but in this case you might want to consider making the
> > clover plugin work the way it did. The clover plugin came before the
> > dashboard plugin. But it's not really a big deal, I just used the old
> > plugin.
>
> Yes, I will w
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 04 December 2003 09:16
> To: Maven Developers List
> Subject: RE: Clover plugin glitches
>
> On Thu, 2003-12-04 at 03:07, Vincent Massol wrote:
> > Argh! Yes it was me. This
On Thu, 2003-12-04 at 03:07, Vincent Massol wrote:
> Argh! Yes it was me. This was not intentional. I was discussing with Bob
> the reason for his on java:compile. We couldn't find the
> reason at that time... Now I understand, it was to prevent the tests
> from being instrumented :-)
>
> Hmm...
Argh! Yes it was me. This was not intentional. I was discussing with Bob
the reason for his on java:compile. We couldn't find the
reason at that time... Now I understand, it was to prevent the tests
from being instrumented :-)
Hmm... That's going to be hard to fix because if we put back the preGo
Although not terribly useful, occasionally looking to see how many of
your tests are running can be elucidating. If the tests aren't running
/ logic in them isn't running, why is it there? Are you not testing
logic paths that you thought you were testing? (i.e. test code isn't
running, hence
On Wed, 2003-12-03 at 19:58, Ben Walding wrote:
> This can be useful behaviour. It should be optional though.
How so? Just never thought about it myself really. But it should be off
by default. If you want to check the integrity of your tests we could
use something like jester.
> Jason van Zyl wr
This can be useful behaviour. It should be optional though.
Jason van Zyl wrote:
Vincent,
It looks like you were the last to modify the clover plugin and it seems
to be instrumenting and reporting on test cases as well. Is this
intentional?
