Without the threading settings? did you change something? I had been getting 0 results running clover:clover. This is because it terminates immediately after the tests complete, before flushing the db. When run under site it works, because other things happen after clover giving the jvm long enough to pick up the thread and flush the db.
- Brett Vincent Massol wrote: > Hi Brett, > > >> -----Original Message----- >> From: Brett Porter [mailto:[EMAIL PROTECTED] >> Sent: vendredi 23 décembre 2005 04:00 >> To: Maven Developers List >> Subject: clover default? >> >> Hi, >> >> I'm wondering what the default for clover should be: >> - everything as now, but set forkmode once when running the tests (this >> is how the cobertura plugin works - I have a patch for this if agreed) >> - set the thread interval settings by default so that forking is not >> required >> >> Thoughts? >> > > The current version of the clover plugin works without requiring to fork the > tests so I believe this is the best solution. I'm currently fixing an issue > in the clover:report goal WRT this but this is working fine. > > Thanks > -Vincent > > > --------------------------------------------------------------------- > 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]
