-
Notifications
You must be signed in to change notification settings - Fork 36
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
Exception when analyzing class with type annotations #68
Comments
When analysis failes an explanation is printed to console, with stacktrace and a link to the github issue #68 The Tests that triggered the failure are included on JDK versions with the problem.
I don't oversee the implications but did you notice that the spring folks seem to have made asm ignore illegal offsets and so that version should be usable on those files? (The spring issue link you provided.) |
I noticed that, but they are actually forking ASM, and I am not interested in doing that. |
The ASM issues referes to https://bugs.openjdk.java.net/browse/JDK-8144185 Looks like the JDK guys agree that it is a JDK issue. |
When analyzing a class with type annotations an exception is thrown like shown below.
This is due to problems that ASM has with the behavior of certain javac versions.
See the following for more details:
If you encounter the problem, you have the following options:
The text was updated successfully, but these errors were encountered: