On Thursday, July 27, 2017 at 11:30:37 AM UTC+2, [email protected] wrote:
Is there any reason as to why the class count value changes between runs? Only classes that are loaded by JVM are dumped. Number of loaded classes might vary from run to run - there are plenty of reasons: non-determinism in application; different actions performed with application in different runs; etc... And similarly number of loaded classes not necessarily includes all the classes of your application. For these reasons - use the original classes from the JAR files of your application to create your report. There are different modules of IT and are not structured in parent child > setup, in order to get aggregated report & > Don't know what you mean by "parent child setup", but the only requirement for use of JaCoCo Maven Plugin goal "report-aggregate" ( http://www.jacoco.org/jacoco/trunk/doc/report-aggregate-mojo.html ) - is that all modules should be part of the same Maven reactor. Alternatively there is JaCoCo Ant Task "report" ( http://www.jacoco.org/jacoco/trunk/doc/ant.html ) that provide great flexibility in specification of files for report. > also to avoid complexities arising due to "runtime changes in classes" > There is pre-instrumentation aka offline instrumentation ( http://www.jacoco.org/jacoco/trunk/doc/offline.html ) to deal with cases if classes are modified at runtime by other tools. -- You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/64d59510-6d72-4145-98d2-8c8576dbf2c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
