-
Notifications
You must be signed in to change notification settings - Fork 742
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
Consider using Multi-Release jars for Error Prone #3756
Comments
Some WIP on this in #4521
|
|
|
copybara-service bot
pushed a commit
that referenced
this issue
Aug 14, 2024
and use it to work around a breaking change in `SignatureGenerator`. #3756 PiperOrigin-RevId: 661672308
copybara-service bot
pushed a commit
that referenced
this issue
Aug 15, 2024
and use it to work around a breaking change in `SignatureGenerator`. #3756 PiperOrigin-RevId: 663105454
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This bug tracks trying to use Multi-Release jar files for Error Prone.
The main use-case is that some checks need to handle AST nodes that not available in all supported JDK versions. Currently we're mostly using reflection to work around that, with mrjars we could move some of that logic behind an internal API and provide implementations that used the new AST nodes for JDK versions that supported them, avoiding the reflection. (e.g. #3737, #3610 (comment))
One of the barriers to doing this is figuring out the best way to produce mrjars with maven. (If anyone reading this has relevant experience, suggestions are welcome!)
The text was updated successfully, but these errors were encountered: