<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi all,<br>
<br>
As tracked by <a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/JBIDE-10537">https://issues.jboss.org/browse/JBIDE-10537</a> , we are
aiming to support Jacoco for code coverage. Jacoco [1] is a very
nice and easy to set up coverage tool that has no significant impact
(in our use-case) on performance [2] , and that only requires a
system property[3] or a maven plugin to set it up in your build [4].
It requires no instrumentation, so it does not requires additional
step in build workflow to get results.<br>
Jacoco's only current drawback is it's missing integration with
Jenkins [5], but as soon as this is available, we will fully drop
support for all the emma stuff to move to Jacoco.<br>
<br>
Waiting for this Jacoco-Jenkins integration, I set up the Maven
plugin in parent and Hudson jobs so that test execution produce a
jacoco.exec file. This file is archived in your build result along
with the output update-site.<br>
See [6] for examples. It is set up for all components jobs on Trunk.
If you don't see this on your job that means that you did not run a
build since this was changed, just start a build to see the
jacoco.exec file in the end.<br>
If you want to have local report, then run "mvn clean install" (or
anything that works and runs tests) in your local component module.
Ensure you are up-to-date with build/ and your-component/ first.<br>
<br>
This jacoco.exec file is pretty easy for you to consume. You can
import it in Eclipse using EclEmma plugin [7] (see [8] for how-to)
and you'll get reports in a dedicated view and also directly on your
source code editor. Beware that your jacoco.exec files has coverage
support for the latest test execution, so file that change it may be
inaccurate when dealing with files that have changed in your
workspace since jacoco.exec was generated.<br>
<br>
Please add feedback to JBIDE-10537<br>
<br>
[1] <a class="moz-txt-link-freetext" href="http://www.eclemma.org/jacoco/">http://www.eclemma.org/jacoco/</a><br>
[2]
<a class="moz-txt-link-freetext" href="http://www.sonarsource.org/pick-your-code-coverage-tool-in-sonar-2-2/">http://www.sonarsource.org/pick-your-code-coverage-tool-in-sonar-2-2/</a><br>
[3] <a class="moz-txt-link-freetext" href="http://www.eclemma.org/jacoco/trunk/doc/agent.html">http://www.eclemma.org/jacoco/trunk/doc/agent.html</a><br>
[4] <a class="moz-txt-link-freetext" href="http://www.eclemma.org/jacoco/trunk/doc/maven.html">http://www.eclemma.org/jacoco/trunk/doc/maven.html</a><br>
[5] <a class="moz-txt-link-freetext" href="https://issues.jenkins-ci.org/browse/JENKINS-10835">https://issues.jenkins-ci.org/browse/JENKINS-10835</a><br>
[6]
<a class="moz-txt-link-freetext" href="http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--examples/">http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--examples/</a><br>
[7] <a class="moz-txt-link-freetext" href="http://www.eclemma.org/installation.html#updatesite">http://www.eclemma.org/installation.html#updatesite</a><br>
[8] <a class="moz-txt-link-freetext" href="http://www.eclemma.org/userdoc/importexport.html">http://www.eclemma.org/userdoc/importexport.html</a><br>
<div class="moz-signature">-- <br>
Mickael Istria<br>
Eclipse developer at <a href="http://www.jboss.org/tools">JBoss,
by Red Hat</a><br>
<a href="http://mickaelistria.wordpress.com">My blog</a> - <a
href="http://twitter.com/mickaelistria">My Tweets</a></div>
</body>
</html>