Hi Igal, 

1. Correct, filtering is implemented as report generation time only.
This is by design to keep the exec file format stable and simplify
configuration: Otherwiese filtering would be required to be configured
at runtime AND analysis time the exact same way and exec file format
would change every time we add new filters. So exec files are and will
not be affected by filtering. (Mabe other features or bug fixes will
change the exec file format in future but not filtering). 

2. Sonar needs to pick-up our next release. Normally this happens quite
quickly. The only way to do it right now is to build a custom version of
Sonar. Please understand that we cannot provide support for our
downstream products. 

Regards,
-marc 

On 2017-12-21 12:23, Igal Kopelman wrote:

> Hi Marc, 
> 
> Thanks for the prompt reply! 
> I just want to see if I understand things right: 
> 
> * The exec file format is not changed and will not be changed in 0.7.10 
> official release and 0.8.0 versions (in respect to the lombok filtering), and 
> this is by design?
> * The Sonar needs to be "updated" (how?) to be able (also) to filter the 
> lombok annotations in the exec file? Is there a way to do that right now, 
> with the 0.7.10-SNAPSHOT?
> 
> Thanks, 
> 
> Igal 
> On Thursday, December 21, 2017 at 12:17:11 PM UTC+2, Marc R. Hoffmann wrote: 
> 
> Hi Igal, 
> 
> your observation is correct: With the new filtering feature in 7.10-SNAPSHOT 
> the exec file format has not been touched. Filtering happens at analysis time 
> (report generation). As long as Sonar does not use a new JaCoCo release it 
> will not support filtering. 
> 
> We hope to release 0.8.0 these days... stay tuned. 
> 
> Cheers,
> -marc 
> 
> On 2017-12-21 10:59, Igal Kopelman wrote: 
> Hello, 
> 
> I are using Lombok plugin in our Java code and interested in getting a true 
> coverage information in the Sonar final report. 
> 
> I am using the Jacoco 7.10-SNAPSHOT version right now and was able (by using 
> the "lombok.addLombokGeneratedAnnotation = true"  in the lombok.config file) 
> to generate a "correct" html jacoco reports - which do ignore correctly the 
> lombok annotations when calculating the code coverage percentage. 
> However - the jacoco.exec file which is also generated, and it's path is 
> passed to the SonarQube, still seems to ignore that  lombok.config file 
> configuration and the coverage which is reflected in it are same as if I am 
> using jacoco 0.7.9 
> 
> Is that by design? Or am I doing something wrong? 
> 
> Thanks, 
> 
> Igal 
> 
> -- 
> 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/ff12bf84-5971-4fab-8781-368974a7adf1%40googlegroups.com
>  [1].
> For more options, visit https://groups.google.com/d/optout [2].

  -- 
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/604df15d-05b7-4b74-836c-d17ce5b398d6%40googlegroups.com
[3].
For more options, visit https://groups.google.com/d/optout. 

  

Links:
------
[1]
https://groups.google.com/d/msgid/jacoco/ff12bf84-5971-4fab-8781-368974a7adf1%40googlegroups.com?utm_medium=email&utm_source=footer
[2] https://groups.google.com/d/optout
[3]
https://groups.google.com/d/msgid/jacoco/604df15d-05b7-4b74-836c-d17ce5b398d6%40googlegroups.com?utm_medium=email&utm_source=footer

-- 
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/c036b5fb72d0f2d28bffa1219b8684e7%40mountainminds.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to