Exclude annotation members from aggressive overloading#453
Exclude annotation members from aggressive overloading#453piazzesiNiccolo-GS merged 2 commits intoGuardsquare:masterfrom
Conversation
|
|
Is there a problem with how the fix for this bug has been implemented? I'd very much like to be able to enable aggressive overloading for one of my projects, and this bug is the only thing preventing me from doing so. |
|
Hi, thanks for the PR! Apologies for the waiting time. Do you have a minimal reproduction of the issue that help us understand how you encountered this? Code looks good, but can you also add an accompanying test? |
|
The issue should occur when the JVM attempts to classload any annotation class with multiple fields which has been aggressively overloaded. The unit test I added contains one such annotation class. |
Perfect, thanks! |



Aggressive overloading class members of annotations can cause errors like this:
This PR excludes annotation class members from aggressive overloading, allowing them to still be obfuscated and for the rest of a project to have aggressive overloading enabled.