-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
track JDK 13 support #2893
Comments
oh and error-prone is also holding us back google/error-prone#1106 |
codefromthecrypt
pushed a commit
that referenced
this issue
Jan 24, 2020
Not concerned about errorprone as it isn't highly value adding anyway. When/if they ever fix the 1.5 year old issue, we can update the profile. Fixes #2893
codefromthecrypt
pushed a commit
that referenced
this issue
Jan 24, 2020
Not concerned about errorprone as it isn't highly value adding anyway. When/if they ever fix the 1.5 year old issue, we can update the profile. Fixes #2893
uhafner
added a commit
to jenkinsci/analysis-model
that referenced
this issue
Jan 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need to retain JRE 1.6 compat, and we use retrolambda to do this. However, retrolambda hasn't had a release in a year and it is broken with java 13 (luontola/retrolambda#154)
Even if we didn't use retrolambda for zipkin's core lib it is a pain. Not about the src/main tree as nothing interesting relies on java 1.8 syntax. More that intellij is too stupid to understand the source difference between src/main and src/test. To date, less than 10 thumbs up https://youtrack.jetbrains.com/issue/IDEA-161060 and honestly I doubt it would change anything anyway as I have another issue with many many more +1s and it is not addressed either. This implies that if we kill retrolambda we also have to move the test source to 1.6 which is annoying because of the neglected intellij issue.
The text was updated successfully, but these errors were encountered: