Clover works on a source code instrumentation level, which means it needs access to source code in order to generate code coverage data.
It works well in multi-module Maven projects, however if you depend on any (external or local) Maven repository to fetch the dependencies (they are not part of multi module project) then you have to manage this by your own. Either by tracking coverage in every module separately (recommended) or by sharing instrumented JAR files (I would rather not recommend it because instrumented JARs can end up in a production system which is rather a bad thing)
Hello everyone, I am a product manager in the Jira Cloud team focused on making sure our customers have a delightful experience using our products. Towards that goal, one of the areas which is extr...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events