-
-
Notifications
You must be signed in to change notification settings - Fork 196
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
Issue #686 Fixed #717
Issue #686 Fixed #717
Conversation
…classes and interfaces. moved code injection validity check to take place after all tokens have been parsed
@Shikib |
The previously compiled jar isn't what's used during the umpleSelf section of the build. To see what the build would look like after the merge, what you should do is |
Yes exactly; you won't see the effect of this PR until it is merged unless you prevent the built jar from being downloaded during the build. |
so I'm merging |
Fixed all of the false positive issues with warning 1012 (invalid code injection). Doesn't falsely generate a warning message for situations where a class is attempting to inject into an extended method.