Lines Matching full:classes

36   Class ids are used to unambiguously identify Java classes. At runtime execution
39   generation — the class ids are used to relate analyzed classes with the
45   The concept of class ids allows distinguishing different versions of classes,
57   in setups where different classes are used at runtime and at analysis time.
60 <h3>What happens if different classes are used at runtime and at analysis time?</h3>
62   In this case execution data cannot be related to the analyzed classes. As a
63   consequence such classes are reported with 0% coverage.
68   The typical symptom of class id mismatch is classes not shown as covered
71   on the top-right corner. You see a list of all classes where execution data
98   classes seen by the JaCoCo runtime agent are different anyways. This typically
108 <h3>What workarounds exist to deal with runtime-modified classes?</h3>
110   If classes get modified at runtime in your setup there are some workarounds to
118       <a href="agent.html">JaCoCo agent</a> and use the dumped classes at report
119       generation. Note that only loaded classes will be dumped, i.e. classes not
122       tests. This way classes get instrumented by JaCoCo before any runtime
124       generated with the <i>original</i> classes, not with instrumented ones.</li>
127 <h3>Why can't JaCoCo simply use the class name to identify classes?</h3>
156   If we would use just slightly different classes at analysis time than at
168   classes). Within the reporting API classes are identified by their fully
170   Therefore it is not possible to include two different classes with the same