Maven multi-module aggregate reports fail to include test results

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Medium
    • 2.1.0
    • Affects Version/s: 2 final
    • Component/s: None
    • None
    • Environment:

      Maven 2.0.7, Clover 2.0b2.1, Plugin 2.0-beta5

      Given the following directory structure:

      • root/master
      • root/submodule1
      • root/submodule2
      • root/...

      When trying to create an aggregated Clover report from the master directory of a mult-module project, I'm witnessing two related problems:

      1) In the generate report (master/target/site/clover/index.html), there are no test results and the error message "No test results could be found. Please ensure that you have configured the location of your test results correctly using the <testresults> nested element." is displayed.

      2) The following error occurs many times during the clover:aggregate goal: WARN: test class not found: com.ducks.deal.ClientSiteServiceImplTest. Obviously, it's repeated for each test class.

      I'm using the command line: mvn clean clover:instrument clover:aggregate clover:clover

      Note that when I use the command line "mvn clean clover:instrument clover:clover" (no aggregate) I get valid, error free reports in each submodule.

      How are we supposed to produce a complete aggregated clover report from master which includes test results?

      It seems like the clover:aggregate goal should gather all of the surefire test results in to target/clover/surefire-reports, or work around the fact that the results are located in the submodule target/clover/surefire-reports directories.

      I've attached the output from "mvn clean clover:instrument clover:aggregate clover:clover".

      Reference: http://www.cenqua.com/forums/thread.jspa?threadID=3257

            Assignee:
            Tom Davies
            Reporter:
            Christian Nelson
            Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: