Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I can't reproduce your problem. I copied and pasted your configuration snippet into a random <code>pom.xml</code> and running any phase posterior to <code>process-classes</code> triggers <a href="http://mojo.codehaus.org/emma-maven-plugin/emma-mojo.html" rel="nofollow noreferrer"><code>emma:emma</code></a> and the coverage report is generated as expected:</p> <pre> $ mvn clean process-classes [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Building Test Project [INFO] task-segment: [clean, process-classes] [INFO] ------------------------------------------------------------------------ [INFO] [clean:clean {execution: default-clean}] [INFO] Deleting directory /home/pascal/tmp/test-project/target [INFO] [resources:resources {execution: default-resources}] [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] [compiler:compile {execution: default-compile}] [INFO] Compiling 1 source file to /home/pascal/tmp/test-project/target/classes [INFO] Preparing emma:emma ... EMMA: runtime coverage data merged into [/home/pascal/tmp/test-project/coverage.ec] {in 93 ms} [INFO] [emma:emma {execution: default}] processing input files ... 2 file(s) read and merged in 3 ms writing [xml] report to [/home/pascal/tmp/test-project/target/site/emma/coverage.xml] ... writing [html] report to [/home/pascal/tmp/test-project/target/site/emma/index.html] ... [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ </pre> <p>Do you have unit tests in your project? Is the <code>coverage.em</code> file non empty? What happens if you run <code>emma:emma</code> on the command line? Does running mvn with the <code>-X</code> option give you any hint? Can you post some traces that would be helpful?</p> <p>As a side note, I wouldn't run <code>emma:emma</code> as part of the regular build personally. I would either run the <code>emma:emma</code> goal from the command line or configure the plugin and the reporting section as suggested in the <a href="http://mojo.codehaus.org/emma-maven-plugin/usage.html" rel="nofollow noreferrer">Usage</a> page. But that's another story and doesn't answer the question.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload