diff options
Diffstat (limited to 'org.jacoco.doc/docroot/doc/faq.html')
| -rw-r--r-- | org.jacoco.doc/docroot/doc/faq.html | 37 |
1 files changed, 29 insertions, 8 deletions
diff --git a/org.jacoco.doc/docroot/doc/faq.html b/org.jacoco.doc/docroot/doc/faq.html index 2e48734e..b24177d7 100644 --- a/org.jacoco.doc/docroot/doc/faq.html +++ b/org.jacoco.doc/docroot/doc/faq.html @@ -14,7 +14,7 @@ <a href="index.html" class="el_group">Documentation</a> > <span class="el_source">FAQ</span> </div> -<div id="content"> +<div id="content"> <h1>FAQ</h1> @@ -29,10 +29,10 @@ guarantee free capacity, we do not commit to particular release dates. Typically, you can expect a couple of releases every year. </p> -<p> +<p> In the <a href="changes.html">change log</a>, you can see all features - that have been been implemented in master branch and will be available - with the next release. And in the meantime you can test latest build of + that have been implemented in master branch and will be available + with the next release. And in the meantime you can test latest build of master branch (<a href="repo.html">Maven SNAPSHOT</a>) and provide <a href="support.html">feedback</a> to us. </p> @@ -45,7 +45,7 @@ <h3>What Java versions are supported by JaCoCo?</h3> <p> - JaCoCo supports Java class files from version 1.0 to 12. However the minimum + JaCoCo supports Java class files from version 1.0 to 16. However the minimum JRE version required by the JaCoCo runtime (e.g. the agent) and the JaCoCo tools is 1.5. Also note that class files under test from version 1.6 and above have to contain valid stackmap frames. @@ -166,7 +166,7 @@ If you use <a href="offline.html">offline instrumentation</a> the instrumented classes get a direct dependency on the JaCoCo runtime. Therefore <code>jacocoagent.jar</code> of the same JaCoCo version must be on the - classpath and accessible from by the instrumented classes. + classpath and accessible from by the instrumented classes. </p> <h3>Why do I get a <code>StackOverflowError</code> during code coverage analysis?</h3> @@ -184,10 +184,31 @@ the <code>-Xss</code> JVM option.</li> </ul> +<h3>Why do I see classes in the coverage report although I excluded them in the JaCoCo agent configuration?</h3> +<p> + The <code>includes</code> and <code>excludes</code> options of the + <a href="agent.html">JaCoCo agent</a> determine for which classes execution + data is collected. Except for technical corner cases these options are + normally not required. If you exclude classes, no execution data is collected + for them. +</p> +<p> + Report creation is a separate step where all class files which should show up + in the report are explicitly provided. Coverage is determined from the + provided execution data. If execution data is missing for a particular class, + this class is shown as not covered because the report generator cannot + distinguish whether the class was excluded from instrumentation or not executed. +</p> + +<p> + If you want to exclude classes from the report please configure the + respective report generation tool accordingly. +</p> + </div> <div class="footer"> - <span class="right"><a href="@jacoco.home.url@">JaCoCo</a> @qualified.bundle.version@</span> - <a href="license.html">Copyright</a> © @copyright.years@ Mountainminds GmbH & Co. KG and Contributors + <span class="right"><a href="${jacoco.home.url}">JaCoCo</a> ${qualified.bundle.version}</span> + <a href="license.html">Copyright</a> © ${copyright.years} Mountainminds GmbH & Co. KG and Contributors </div> </body> |