Answers to: Jacoco in Maven Build

Comment by TareqK on TareqK's answer

TareqK — Mon, 13 Jan 2020 10:29:10 -0500

@Reguel Thanks for the feedback, ill try it out as soon as i can!

Comment by Reguel Wermelinger on TareqK's answer

Reguel Wermelinger — Mon, 13 Jan 2020 10:18:44 -0500

Cool solution: thanks for sharing!

One remark though:

you can make the resource copy process slightly simpler by teaching ivy projects where to put compile classes into (our default /classes is not the best for maven natured projects)
use the package explorer > context menu > properties > java build path > source
set the settings outlined in the screenshot:

Answer by TareqK

TareqK — Mon, 13 Jan 2020 10:07:53 -0500

Updates on this :

Got it to work, turns out as @Reguel said, the JDT compiler wont play with a javaagent. I got around this by using the offline mode of jacoco, and copying the generated classes from the classes directory in the correct target/classes and target/test-classes directories . This is what the pom section looks like :

Gist Of pom.xml parts

You also need to set the <testoutputdirectory> as well, otherwise it wont work

The reports are generated in the target/site/jacoco folder, and the jacoco.exec file is in the target folder as well

Comment by Reguel Wermelinger on TareqK's question

Reguel Wermelinger — Fri, 10 Jan 2020 05:22:07 -0500

you may have to set explicitly the test releated vars in pom.xml: e.g.

<build>
    <testSourceDirectory>src_test</testSourceDirectory>
    <testOutputDirectory>target/test-classes</testOutputDirectory>
</build>

if that doesn't help: the issue is very likely that jacoco works with a javaagent. Since we setup a custom JDT compiler run, this agent may can not be made known with a standard approach.

However, we can provide detailed feedback if you share a simple project that shows the issue and file it as official support request.

Comment by TareqK on TareqK's question

TareqK — Thu, 09 Jan 2020 09:01:39 -0500

I Did indeed do the maven setup, im using maven 4.12 with powermock and mockito, and all the test do run. I checked this configuration compared to the examples on baeldug and mkyong, but still no luck. Jacoco does see all the packages, its just ignoring every class in them.

Comment by Lukas Lieb on TareqK's question

Lukas Lieb — Thu, 09 Jan 2020 08:39:31 -0500

Seems to be an maven configuration problem to me... How do you configure you're maven build? Do you use the jacoco-maven-plugin? Did the tests run? Which JUnit version? Maybe this blog post can help you: https://www.mkyong.com/maven/maven-jacoco-code-coverage-example/

Kind regards

Lukas