New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generated annotation filter detection does not work when used with parameters #831
Comments
Hi, This has nothing to do with parameters, because as you can see Google's Dagger annotation processor uses either Annotations with parameters having correct retention policy are processed correctly: given
execution of
produces as expected. |
Thanks for the detailed reply. I actually searched before posting but couldn't find it. Here is 2 feedback:
|
Noted, will improve.
No - source code parsing is out of scope of project, not even recalling/considering that JaCoCo supports Kotlin and Groovy. |
That makes sense. 😊 Thanks a lot. |
Steps to reproduce
JaCoCo version: 0.8.2
Operating system: MacOS
Tool integration: Gradle
Expected behaviour
Class generated with
@Generated
annotation with parameters should also be ignored from code coverage report.It is pretty easily reproducable when used by Google's Dagger annotation processor. They put something like below on top of generated classes
Actual behaviour
Not just simple usage of
@Generated
annotation but all versions should be ignored.The text was updated successfully, but these errors were encountered: