-
Notifications
You must be signed in to change notification settings - Fork 39
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
Document minimum version of Error Prone required #724
Comments
Hey @chrismgrayftsinc! Great idea; I'll leave this issue open as a reminder that we should add such a table. (Bit swamped at the moment, so it may take a bit. And I'll check whether this can be automated 😅.) Tnx for trying Error Prone Support! |
Due to the way in which Refaster rules are serialized, most of the time a version of Error Prone Support is only compatible with the version of Error Prone against which it is built. For Just dropping here a small script that lists the version of Error Prone against which each Error Prone Support was built. To be generalized later.
|
The new `website/generate-version-compatibility-overview.sh` script tests all combinations, and stores the result in a Jekyll data file. Resolves #724.
Hey @chrismgrayftsinc! It's been a while, but the compatibility information is now published on the website. If you're interested in the details, see #938. |
The new `website/generate-version-compatibility-overview.sh` script tests all combinations, and stores the result in a Jekyll data file. Resolves #724.
The new `website/generate-version-compatibility-overview.sh` script tests all combinations, and stores the result in a Jekyll data file. Resolves #724.
The new `website/generate-version-compatibility-overview.sh` script tests all combinations, and stores the result in a Jekyll data file. Resolves #724.
Problem
I was attempting to run the latest version of the rules using the version of errorprone built in to bazel 5.2.1. This failed because it appears the latest version only works with versions of errorprone > 2.20.0 (or so). I was not able to find any documentation of that, but there are some closed issues where people had similar problems. It may make sense to have a compatibility matrix or something prominent in the documentation.
The text was updated successfully, but these errors were encountered: