-
Bug
-
Resolution: Fixed
-
Low
-
3.0 M4
-
None
-
Windows 7, Maven 2.0.10, Java 1.6.0_18, gmaven_plugin 1.0-rc-5, Groovy 1.6.2
There is something strange going on with the classpath when building combined Java and Groovy Maven modules instrumented by Clover. If I run the build without Clover, it completes OK. If I apply the following binding in the POM, it fails:
<plugin>
<groupId>com.atlassian.maven.plugins</groupId>
<artifactId>maven-clover2-plugin</artifactId>
<version>3.0.0-m4r3</version>
<executions>
<execution>
<id>instrument</id>
<phase>process-sources</phase>
<goals>
<goal>setup</goal>
</goals>
</execution>
<execution>
<id>report</id>
<phase>verify</phase>
<goals>
<goal>clover</goal>
</goals>
</execution>
</executions>
</plugin>
It is giving errors like this:
C:\Users\amcmanus\Documents\Temp\clov-920\target\clover\src-instrumented\org\oclc\test\InJava.java:[20,12] cannot find symbol symbol : class Thingumy location: class org.oclc.test.InJava
(where Thingumy is a Groovy class).
Test case to follow shortly...
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
