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

Maven-clover-plug-in and Eclipse-Clover-plug in give different coverage results.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Medium Medium
    • won't fix
    • 2.1.0
    • None
    • None

    • Eclipse V3.2, Eclipse Clover Plug-in v2.1.0, Maven-clover-plug-in V3.7. OS windows XP

      I have a project for which the Clover plug in for eclipse reports a coverage of 88.7%, but the Maven-clover-plug-in reports code coverage of 81.2%.

      I suspect that the variation is caused by the includes, excludes settings.

      I've set the includes in the Eclipse plugin as:

      src/main/java/*/.java

      and the excludes as:

      src/test/java/*/.java

      In the maven pom file I've configured the excludes as:

      <excludes>
      <exclude>src/test/java/*/.java</exclude>
      </excludes>

      but whenever I add:

      <includes>
      <include>src/main/java/*/.java</include>
      </includes>

      The maven colver plug in reports that no sources could be found.

      Thanks,

      Peter Johnstone

            [CLOV-194] Maven-clover-plug-in and Eclipse-Clover-plug in give different coverage results.

            Nick added a comment -

            Both these issues have been raised against the maven plugin

            Nick added a comment - Both these issues have been raised against the maven plugin

            Peter Johnstone added a comment -

            Clover instrument issue: CLOV-218

            Clover clean / includes issue: CLOV-219

            Peter Johnstone added a comment - Clover instrument issue: CLOV-218 Clover clean / includes issue: CLOV-219

            Peter Johnstone added a comment - - edited

            Further information on this issue:

            I've managed to get the includes section working in the projects parent pom, and have discovered that when the includes section in the parent pom matches those in eclipse, the clover results for the project still do not match.

            I have also discovered that if the clean goal is specified and the project pom contains include entries, then the project skips the clover report generation reporting that it cant find the clover database.

            Additionally if I try running the clover:instrument goal using an evaluation license, clover reports that the license has expired even although I still have some time left on the evaluation license.

            I realise that these are seperate issues, so I will raise these separately and add links in a further comment once I have done so.

            Thanks,

            Peter Johnstone.

            Peter Johnstone added a comment - - edited Further information on this issue: I've managed to get the includes section working in the projects parent pom, and have discovered that when the includes section in the parent pom matches those in eclipse, the clover results for the project still do not match. I have also discovered that if the clean goal is specified and the project pom contains include entries, then the project skips the clover report generation reporting that it cant find the clover database. Additionally if I try running the clover:instrument goal using an evaluation license, clover reports that the license has expired even although I still have some time left on the evaluation license. I realise that these are seperate issues, so I will raise these separately and add links in a further comment once I have done so. Thanks, Peter Johnstone.

              npellow Nick
              1d6c5a7445c5 Peter Johnstone
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: