-
Notifications
You must be signed in to change notification settings - Fork 744
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
HidingField: NoSuchMethodError: 'com.sun.tools.javac.util.List com.sun.tools.javac.code.Symbol$TypeSymbol.getEnclosedElements #2092
Comments
This release was built against a newer JDK and picked up this backwards-incompatible change: openjdk/jdk@827e5e3#diff-9b6c5d86aacec00206bfcdbfc12caa41fbb0812426c4f2fd290c3fb1873a532fR840 I can work around that specific example, but if there are a lot more examples of this we should go back to building the release against JDK 8. Do you mind disabling that particular check with |
Our codebase appears to compile with that disabled |
The same on my side - with |
This issue looks similar, even if the BugPattern is ComputeIfAbsentAmbiguousReference
|
Same error here. Using JDK 8. |
Thanks for the additional reports. #2092 (comment) looks like a distinct issue with the same root cause. I'm going to release a 2.5.1 built on JDK 8 that will resolve this issue. |
Fwiw, the release notes mention JDK 8, but it's also an issue with JDK 11 (or apparently any version before JDK 15 according to the JDK commit you linked to). That said, thanks for the fix and the release! |
@tbroyer I updated the relnotes, thanks for the correction! |
@cushon FYI I just saw this issue on JDK 11 when trying to update from Error Prone 2.18.0 to Error Prone 2.19.0. Is this unexpected? We can disable the |
* Bump com.google.errorprone:error_prone_core from 2.18.0 to 2.19.0 Bumps [com.google.errorprone:error_prone_core](https://github.com/google/error-prone) from 2.18.0 to 2.19.0. - [Release notes](https://github.com/google/error-prone/releases) - [Commits](google/error-prone@v2.18.0...v2.19.0) --- updated-dependencies: - dependency-name: com.google.errorprone:error_prone_core dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> * applied suggested workaround for compiling with jdk 11 See here: google/error-prone#3895 and google/error-prone#2092 --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: -Denux <83671398+DenuxPlays@users.noreply.github.com>
Description of the problem:
After upgrading errorprone from 2.4.0 to 2.5.0 following is reported in [my project's] maven build (with JDK8, JDK11, JDK12 or JDK13):
The same code works fine with JDK14 and JDK15.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
What version of Error Prone are you using?
2.5.0
Have you found anything relevant by searching the web?
#1529
The text was updated successfully, but these errors were encountered: