We need to prove we can measure coverage for a given project by combining coverage db from various test projects.
Our structure goes as follows:
None of this projects share a parent pom, nor can they.
This is what I've tried:
//instrument project-src-x binaries $ project-src-x: mvn clean clover:setup install //run project-it-y tests $ project-it-y: mvn clean clover:setup -Dmaven.clover.cloverDatabase=/tmp/clover-y.db //run project-ut-z tests $ project-ut-z: mvn clean clover:setup -Dmaven.clover.cloverDatabase=/tmp/clover-z.db //merge clover dbs and generate report $ project-src-x : mvn clean clover:merge -Dmaven.clover.merge.basedir=/tmp/ clover:clover
The resulting report has no information about project-src-x at all.
I know both test projects are using the instrumented code of project-src-x because I needed to include clover's jar in order to execute them.
What can be the problem here?
Thanks in advance,
$ project-src-x: mvn clean clover:setup install
Where do you write clover.db file for this project? As you run clover:merge with -Dmaven.clover.merge.basedir=/tmp, then I assume that for project-src-x you should write clover.db to /tmp as well. And the most probably you write it to standard location (<project-src-x dir>/target/clover).
Please try to run:
mvn clean clover:setup install -Dmaven.clover.cloverDatabase=/tmp/clover.db
Hello Atlassian Community! My name is Emilee, and I’m a Product Marketing Manager for the Marketplace team. Starting with this post, I'm kicking off a monthly series of Spotlights to highlight Ma...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot