>From Maven Clover Plugin page: clover2:instrument<http://docs.atlassian.com/maven-clover2-plugin/2.3.1/instrument-mojo.html> No Instrument all sources using Clover and forks a custom lifecycle to execute project's tests on the instrumented code so that a Clover database is created. It clearly states that executes projects tests, so it fires the test phase. This is probably the problem. It is missing the test resources. Check in classes an test-classes dirs to see if there are the needed files. Maybe you need to add the resources plugin prior to clover instrument? Again, if you post the maven output it will help. Check which goals are being executed when launching mvn site.
Josep 2010/11/30 Milbourne, Anthony <anthony.milbou...@credit-suisse.com> > Josep, > > I believe mvn site should call the lifecycle up to the site phase, so that > would be: pre-site & site phases. > > If process-test-resources is necessary to run Hibernate (I can see the > logic there), how come running mvn site works fine - it is just the Clover > profile that breaks Hibernate (mvn site -Pclover)? > > Thanks, > > Anthony. > > ------------------------------ > On the 30 November 2010 14:17 Josep García Wrote: > mvn site has its own lifecycle, and does not incluce > process-test-resources. > > > http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html > > What is the output in the console? Which are the goals executed when you > issue mvn site? > > Josep > > 2010/11/30 Anthony > > Hi All, >> >> I am using the 2.1.0-M1 version of the modular spring archetype and I'm >> trying to get Clover (3.0.2) working with AppFuse and I seem to be going >> backwards :-(. >> >> I have added a clover profile, as below (I have tried adding it to the top >> level POM and the core sub-POM): >> >> <profile> >> <id>clover</id> >> <build> >> <plugins> >> <plugin> >> <groupId>com.atlassian.maven.plugins</groupId> >> <artifactId>maven-clover2-plugin</artifactId> >> <configuration> >> <license> >> <![CDATA[OURLICENSEKEY]]> >> </license> >> </configuration> >> <executions> >> <execution> >> <id>clover</id> >> <phase>verify</phase> >> <goals> >> <goal>instrument</goal> >> <goal>aggregate</goal> >> </goals> >> </execution> >> <execution> >> <phase>pre-site</phase> >> <goals> >> <goal>instrument</goal> >> <goal>aggregate</goal> >> </goals> >> </execution> >> </executions> >> </plugin> >> </plugins> >> </build> >> <reporting> >> <plugins> >> <plugin> >> <groupId>com.atlassian.maven.plugins</groupId> >> <artifactId>maven-clover2-plugin</artifactId> >> </plugin> >> </plugins> >> </reporting> >> </profile> >> >> This seemed to conflict with the canoo testes in the web module so I >> commented out the activation block that caused canoo to run, as so: >> >> <!--activation> >> <property> >> <name>!skipTests</name> >> </property> >> </activation--> >> >> I now have to run canoo manually with mvn verify -Pintegration-test, but >> I can build the project and Clover does appear to run when I specify mvn >> verify -Pclover. However, if I run mvn site -Pclover I get an error from >> Hibernate as below: >> >> The dialect was not set. Set the property hibernate.dialect. >> >> Even if I explicitly set the DB profile with something like mvn site >> -Pclover,h2 it still fails with the same error. >> >> *Has anyone else got Clover working with AppFuse?* Matt, I read another >> post where you mentioned that you used Clover, but I couldn't find any more >> details apart from Dustin >> Pearce-2<http://appfuse.547863.n4.nabble.com/template/NamlServlet.jtp?macro=user_nodes&user=37190>'s >> suggestion to add a dependency (which didn't seem to fix things). >> >> Thanks, >> >> Anthony. >> > > > ============================================================================== > Please access the attached hyperlink for an important electronic > communications disclaimer: > http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html > > ============================================================================== > >
