-
Notifications
You must be signed in to change notification settings - Fork 745
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
Release Error Prone 2.4.0 #1639
Comments
Great news! Waiting for EP 2.4.0 to show up, so that I can bump outdated and actually unknown EP version in Bazel (2.3.2-SNAPSHOT version is currently used there). |
Thanks @davido! Have you had a chance to test the latest snapshot of EP against Bazel's CI? |
Sure! Already build EP 2.3.5-SNAPSHOT that includes all your recent changes and uploaded a new version of my PR (forced push). Unfortunately, the outdated Android SDK used in Bazel, that still depends on outdated Guava library causing all Android tests in Bazel to fail. I have also built Next step is to use EP 2.4.0 for "java_tools_java14.zip" work. Hope to upload a PR for review ASAP (jdk.compiler module is missing, but i think it can be skipped in the toolchain definition). [1] https://github.com/davido/java_tools/releases/tag/javac11-v12.0 |
I think Error Prone is still compatible with |
Anyway, let me know if the latest snapshot looks sane to you, and I can go ahead it release it. We can always do a point release if additional testing with Bazel reveals other issues. |
Thanks for clarifying, let me try to downgrade |
Thanks, @cushon. After downgrading I have also tested Gerrit and JGit againt latest EP snapshot and have not found any issues. Looks sane to me. I think you can go ahead and release it ;-) Thanks again for demoting problematic bug patterns that broke Bazel cross compilation use case from error severity to warning and adding JDK 14 support! Update: I created [1] https://github.com/davido/java_tools/releases/tag/v14.0 |
As a quick update, I found a few crashes while validating the release, and I'm preparing fixes for those. I'll cut the 2.4.0 release as soon as those fixes land. |
Discovered while validating 2.4.0 release (#1639) ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=313480851
Discovered while validating 2.4.0 release (#1639) ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=313487177
Discovered while validating 2.4.0 release (#1639) ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=313488001
Discovered while validating 2.4.0 release (#1639) ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=313496085
#1639 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=313686571
Discovered while validating 2.4.0 release (#1639) ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=313711584
Discovered while validating 2.4.0 release (#1639) ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=313480851
Discovered while validating 2.4.0 release (#1639) ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=313487177
Discovered while validating 2.4.0 release (#1639) ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=313488001
Discovered while validating 2.4.0 release (#1639) ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=313496085
#1639 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=313686571
Discovered while validating 2.4.0 release (#1639) ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=313711584
Tracking bug for 2.4.0 release.
The text was updated successfully, but these errors were encountered: