Hi Andy,

I am using maven beta 9 version and clover 1.0. and
if I run the command "maven clover:test"  it says no such target exists.
and as I mentioned earlier, I am executing the same using two seperate
commands.
and my source directory and unit test source directory are same.
and also I am having the maven.junit.fork=true property in
project.properties.

but still I am getting..the same error..

RK

-----Original Message-----
From: Andy Pols [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2003 11:48 AM
To: Maven Users List
Subject: Re: Clover generates 0% code coverage reports


The problem is that clover database logs are written on JVM shutdown.
Thus if you call the clover test goal and then the report immediately
after, you'll get an empty report.

There are two solutions:

So, to make it work, simply run :

maven clover:test

and then, in a separate command:

maven clover:html-report



Or placing the following in the project.properties file should also work:
maven.junit.fork = true

Andy

On 17/6/03 6:38 am, "S. Radhakrishnan" <[EMAIL PROTECTED]> wrote:

> Hi I am using maven beta 9 and clover 1.0. after referred the sites i am
> doing the clover test and clover report in two seperate commands
>> maven clover test
>> maven clover
> but still the report gives 0% code coverage. Is there any wrong in the
> clover plugin ?.. please can anybody help me out.
>
>
> Thanks & Regards,
> S.Radhakrishnan,
>
>
>
> ---------------------------------------------------------------------
> 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]

Reply via email to