On Wednesday, October 26, 2016 at 4:16:29 AM UTC-7, Evgeny Mandrikov wrote: > Those steps are too generic, so I wouldn't name them as reproducer. And they > are covered by our integration tests. By reproducer I meant a small example > project, which we would be able to execute. > > > And anyway I would advice you to try latest JaCoCo version 0.7.7 with option > "inclnolocationclasses=true", because once again - this is the only notable > change between 0.7.2 and 0.7.3. > > On Wednesday, October 26, 2016 at 12:28:44 AM UTC+2, [email protected] > wrote:On Tuesday, October 25, 2016 at 2:45:18 PM UTC-7, Evgeny Mandrikov > wrote: > > > This sounds really weird, because there is no other changes between 0.7.2 > > and 0.7.3 that could lead to this. Might it be a misconfiguration on your > > side? Could you provide a small reproducer? > > > > > > On Tuesday, October 25, 2016 at 10:30:01 PM UTC+2, [email protected] > > wrote:On Friday, October 21, 2016 at 4:00:04 AM UTC-7, Marc R. Hoffmann > > wrote: > > > > Hi, > > > > > > > > exclusion of dynamically generated classes only applies to runtime. For > > > > report generation these classes have never been shown. So I don't think > > > > this causes the difference. > > > > > > > > When you compare both reports please drill down to a specific class > > > > where you see differences and show differences here (e.g. with > > > > screenshots). > > > > > > > > Regards, > > > > -marc > > > > > > > > > > > > On 2016-10-21 00:05, john.mak wrote: > > > > > When doing on-the-fly instrumentation and reporting on the same > > > > > code/test run I noticed that the coverage % dropped starting in JaCoCo > > > > > 0.7.3. It seem like it was due to a new feature that excluded > > > > > dynamically generated classes. Is there an option to disable this > > > > > feature? If not I will be stuck using 0.7.2. Thanks. > > > Hi Marc, thanks for the reply but after looking at this some more the > > classes with this issue are not dynamically generated so it must be some > > other cause. > > > > There are no configuration changes, the only difference is the JaCoCo > version. Here are the detailed steps of what I am doing, it might be this > sequence of steps that this issue occurs. > > > > 1. Execute my java unit and integration tests via maven using > jacoco-maven-plugin > > 2. jacoco-ut.exec and jacoco-it.exec files generated for all the different > projects > > 3. Merge all the .exec files into one file using jacoco-maven-plugin > > 4. Generate coverage html report on the merged .exec file using the jacoco > Ant report task
Thanks Evgeny. I'll try out 0.7.7 with inclnolocationclasses=true -- 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/a41d5a78-6cb7-4999-a209-69e203e61139%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
