Hi Pavel, This is strange because the Clover plugin simpy delegate the execution of tests to the test:test goal. In other Clover is transparent there.
Could it be the fact that the tests are executed twice? Here's what you can try: - Tell the Clover plugin not to run the tests by setting the maven.clover.execute.during.report to false for all your projects. - Ensure your code is clovered before your unit tests are run. For this to work, simply run "maven clover:on site" instead of "maven site" (or "maven clover:on multiproject:site" instead of "maven multiproject:site"). I'm still curious to understand why the MAVEN_OPTS stuff does not work though but I don't see anything in the Clover report that would make it not use a system property. Thanks -Vincent > -----Original Message----- > From: Pavel M�ller [mailto:[EMAIL PROTECTED] > Sent: mercredi 20 avril 2005 20:47 > To: [email protected] > Subject: Clover plugin & MAVEN_OPTS > > Hi, > I've got a working Maven build on Windows, but I've decided to generate a > site every night on my Linux server. Some of my unit tests require AWT > graphics (because of JasperReports), so they do not pass until I set > MAVEN_OPTS=-Djava.awt.headless=true. > But when generating a site the tests are run twice. Tests for unit test > report pass, but the same tests run by Clover plugin fails. It is because > the Clover plugin doesn't get the headless option. I tried to set ANT_OPTS > too, but it didn't work. > Is there a way to tell the Clover plugin to use MAVEN_OPTS. Or am I doing > anything wrong? > > Thank you > Pavel > > > --------------------------------------------------------------------- > 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]
