Lines Matching +full:minimal +full:- +full:versions
1 <?xml version="1.0" encoding="UTF-8" ?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-st…
5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
6 <link rel="stylesheet" href="resources/doc.css" charset="UTF-8" type="text/css" />
8 <title>JaCoCo - Class Ids</title>
28 Class ids are 64-bit integer values, for example
45 The concept of class ids allows distinguishing different versions of classes,
46 for example when multiple versions of an application are deployed to an
47 application server or different versions of libraries are included.
50 Also class ids are the prerequisite for JaCoCo's minimal runtime-overhead and
71 on the top-right corner. You see a list of all classes where execution data
80 Class ids are identical for the exact same class file only (byte-by-byte).
87 <li>Different compiler versions</li>
88 <li>Different compiler settings (e.g. debug vs. non-debug) </li>
91 Also post-processing class files (obfuscation, AspectJ, etc.) will typically
100 or special class loaders pre-process the class files. Typical candidates are:
108 <h3>What workarounds exist to deal with runtime-modified classes?</h3>
120 executed at all will not show-up in your report as not covered.</li>
136 called <i>instrumentation</i>. To keep the runtime overhead minimal, only a
158 we would end-up with different probes. For example the probe at index
163 <h3>Why do I get an error when I try to analyze multiple versions of the same
171 name within a group. Anyhow it is possible to analyze different versions of