Lines Matching full:jacoco
8 <title>JaCoCo - FAQ</title>
13 <a href="../index.html" class="el_report">JaCoCo</a> >
22 This is a compilation of questions that have been asked by JaCoCo users
28 JaCoCo is maintained by volunteers in their free time. Since we cannot
40 <h3>Does JaCoCo have a plug-in for [Eclipse|Netbeans|Whatever...]?</h3>
46 <h3>What Java versions are supported by JaCoCo?</h3>
48 JaCoCo supports Java class files from version 1.0 to 16. However the minimum
49 JRE version required by the JaCoCo runtime (e.g. the agent) and the JaCoCo
57 names. You get this error during report generation if JaCoCo is supplied with
64 JaCoCo determines code execution with so called probes. Probes are inserted
73 JaCoCo is based on class files analysis. To calculate line coverage class
81 highlighting in JaCoCo coverage reports:
111 Yes, there are three possible ways: The JaCoCo <a href="agent.html">agent</a>
120 Alternatively the JaCoCo <a href="agent.html">agent</a> can be configured to
122 <code><a href="./api/org/jacoco/agent/rt/IAgent.html">org.jacoco:type=Runtime</a></code>
126 In addition JaCoCo provides a <a href="./api/org/jacoco/agent/rt/RT.html">Java API</a>
130 <h3>My code uses reflection. Why does it fail when I execute it with JaCoCo?</h3>
132 To collect execution data JaCoCo instruments the classes under test which adds
145 JaCoCo can instrument valid class files only. Class files with syntactical or
146 semantical error will typically lead to exceptions. In certain areas JaCoCo is
147 more restrictive then the JVM: JaCoCo expects valid so-called "stackmap
148 frame" information in class files of version 1.6 or higher. In turn JaCoCo
156 <h3>Does JaCoCo run on the IBM JRE J9 and WebSphere?</h3>
158 It does. To make the JaCoCo agent work please set the VM option
164 <code>org.jacoco.agent[...]Offline</code>?</h3>
167 classes get a direct dependency on the JaCoCo runtime. Therefore
168 <code>jacocoagent.jar</code> of the same JaCoCo version must be on the
177 <li>Misconfiguration: If you configure two JaCoCo agents of different releases
180 <li>Heavy stack usage: JaCoCo instrumentation adds a small runtime overhead
187 <h3>Why do I see classes in the coverage report although I excluded them in the JaCoCo agent config…
190 <a href="agent.html">JaCoCo agent</a> determine for which classes execution
210 <span class="right"><a href="${jacoco.home.url}">JaCoCo</a> ${qualified.bundle.version}</span>