-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Support for running in Java 19 by upgrading ASM #1654
Comments
jaroslawr
added a commit
to jaroslawr/guice
that referenced
this issue
Nov 18, 2022
Has there been any movement on this? It appears as though #1657 covers this issue. |
Nava2
added a commit
to kaff4/kaff4
that referenced
this issue
Mar 19, 2023
Due to google/guice#1654 Java 17 is the max version supported.
Nava2
added a commit
to kaff4/kaff4
that referenced
this issue
Mar 19, 2023
Due to google/guice#1654 Java 17 is the max version supported.
Nava2
added a commit
to kaff4/kaff4
that referenced
this issue
Mar 19, 2023
Due to google/guice#1654 Java 17 is the max version supported.
copybara-service bot
pushed a commit
that referenced
this issue
Apr 14, 2023
…sses with ASM, so Guice is less finicky about the precise .class version & ASM version. A while ago I had tried to do this by ignoring UnsupportedOperationException, but per #1654, ASM doesn't always throw UOE. This change will log a single failure when Guice encounters an exception while reading classfiles and warn that ASM may be out of date. The consequences of this failing _all_ line number reading (due to, say, an accidental bug introduced while parsing classfiles) is that Guice won't emit line numbers for bind statements in modules (as binding source locations). A number of other tests would fail in that scenario, warning us that something is off. PiperOrigin-RevId: 524365509
copybara-service bot
pushed a commit
that referenced
this issue
Apr 14, 2023
…sses with ASM, so Guice is less finicky about the precise .class version & ASM version. A while ago I had tried to do this by ignoring UnsupportedOperationException, but per #1654, ASM doesn't always throw UOE. This change will log a single failure when Guice encounters an exception while reading classfiles and warn that ASM may be out of date. The consequences of this failing _all_ line number reading (due to, say, an accidental bug introduced while parsing classfiles) is that Guice won't emit line numbers for bind statements in modules (as binding source locations). A number of other tests would fail in that scenario, warning us that something is off. PiperOrigin-RevId: 524387180
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The bundled ASM 9.2 doesn't support reading Java 19 class file version 63. While class generation works fine, the error reporting functionality throws the following error
The text was updated successfully, but these errors were encountered: