Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Don't fail if there are no tests to mutate

See original GitHub issue

I added a new module in my maven project which only contains resources, and our “QA” build that runs pitest failed:

[INFO] --- pitest-maven:1.1.4:mutationCoverage (default-cli) @ persistency-model ---
[INFO] Found plugin : Default csv report plugin
[INFO] Found plugin : Default xml report plugin
[INFO] Found plugin : Default html report plugin
[INFO] Found plugin : Default limit mutations plugin
[INFO] Found shared classpath plugin : Default mutation engine
52:35 AM PIT >> INFO : Mutating from /home/bamboo/bamboo-agent-home/xml-data/build-dir/COL-QA-JOB1/persistency-model/target/classes
6:52:35 AM PIT >> INFO : Verbose logging is disabled. If you encounter an problem please enable it before reporting an issue.
6:52:36 AM PIT >> INFO : Sending 0 test classes to slave
6:52:36 AM PIT >> INFO : Sent tests to slave
6:52:36 AM PIT >> INFO : Calculated coverage in 0 seconds.
6:52:36 AM PIT >> INFO : Created  0 mutation test units
[...]
[ERROR] Failed to execute goal org.pitest:pitest-maven:1.1.4:mutationCoverage (default-cli) on project persistency-model: Execution default-cli of goal org.pitest:pitest-maven:1.1.4:mutationCoverage failed: No mutations found. This probably means there is an issue with either the supplied classpath or filters.

This module doesn’t have any java source files.

It would be really nice if the mutationCoverage goal would simply skip this project, just like the maven compiler/surefire/etc plugins do.