Uploaded image for project: 'Clover'
  1. Clover
  2. CLOV-928

Groovy classes are not visible from Java when instrumented by Clover within Maven lifecycle

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 3.0 M5, 3.0
    • 3.0 M4
    • Groovy, Maven plugin
    • 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...

        1. clov-928.tar.gz
          11 kB
        2. clov-928.zip
          21 kB

          1.
          		 Document the need for maven-clover2-plugin:setup to run before gmaven:generateStubs (DRAFT COMPLETE) Sub-task Closed Giles Gaskell [Atlassian]

            [CLOV-928] Groovy classes are not visible from Java when instrumented by Clover within Maven lifecycle

            Owen made changes -
            Workflow Original: New Clover Workflow [ 897969 ] New: New Clover Workflow - Restricted [ 1475015 ]
            Piotr Swiecicki made changes -
            Workflow Original: Clover Workflow [ 896225 ] New: New Clover Workflow [ 897969 ]
            Piotr Swiecicki made changes -
            Workflow Original: reviewflow [ 208080 ] New: Clover Workflow [ 896225 ]
            Nick made changes -
            Fix Version/s New: 3.0 M5 [ 15131 ]
            Fix Version/s New: 3.0 [ 14870 ]
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]
            Nick made changes -
            Attachment New: clov-928.tar.gz [ 37343 ]
            Nick made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]
            Nick made changes -
            Assignee New: Nick [ npellow ]
            Alex McManus made changes -
            Attachment New: clov-928.zip [ 37336 ]
            Alex McManus created issue -

              npellow Nick
              2aceeb5c9a94 Alex McManus
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: