Thanks for taking the time to reply Evgeny. The fake test solution was the first thing we tried, and found that ti didn't work unless we explicitly called code in the module within the test. A dummy test was not enough to force a report to be generated.
In the end we decided to go with adding some flags to the parent pom the 100 or so projects inherit from that fails if a module doesn't have tests. Leaving this reply just so any future searchers can come across it. On Tuesday, March 19, 2019 at 4:00:48 PM UTC, Evgeny Mandrikov wrote: > On Tuesday, March 19, 2019 at 4:31:04 PM UTC+1, [email protected] wrote: > Is this option exposed in the jacoco maven plugin? > > > All configuration parameters are listed in documentation - > https://www.jacoco.org/jacoco/trunk/doc/report-mojo.html > Furthermore all source code of jacoco-maven-plugin is also available - > https://github.com/jacoco/jacoco/tree/master/jacoco-maven-plugin > > > > > Is there any way to force the creation of a jacoco.exec file that just says > there were no lines covered at all? > > > > Just create literally empty "jacoco.exec" file. > > > > > Or even simpler - just create literally empty test, so that it will be > executed and "jacoco.exec" will be created for you: > > > public class FakeTest { > @org.junit.Test > public void empty() { > } > } -- You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/8d5d6416-80b5-43c3-a9e4-3dfecef877d1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
