-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
An alts
release built with JDK 9+ wouldn't work under Java 7 or 8
#7348
Comments
(Also, if you know of other projects who are likely to be affected (Google-run or otherwise), please spread the word.) |
I'm so very sorry for whatever your day must have been like. Those commands say it all. 🤣 Except then I looked at protocolbuffers/protobuf#7827 and there was more! Yes, we build with Java 8. When I saw #6839 I wondered why animalsniffer didn't notice; but I also didn't understand our change (not enough context was given; thanks for this wonderful report). I'm not wild about the approach taken in #6839; I'd much rather downcast to Buffer manually at each limit location or use a utility that implicitly does the same, but without an automated checker there's likely regressions no matter the approach. It seems like we should just give animalsniffer a bit more time to fix this. I've subscribed to the issue and PR so I can upgrade the version when released. We aren't at risk of swapping to Java 11 for compilation of our releases within the next ~year. I'm strongly tempted to make changes now, but I know there's some PRs in flight that would immediately regress our state. So I'm just going to leave things "as-is" until we have a way to prevent regressions. CC @voidzcy |
Yes, I also noticed the existing awkwardness (take in a |
From #6829 (comment), I gather that your process may be to build releases with JDK 8. If so, then this is more about convenience for anyone else who might do a local build. (Compare #6839, which dealt with similar calls in
core
.)My attempt to turn up other such calls shows some in
alts
:Again, there is no problem with 1.31.1, which I assume you built with JDK 8:
Still, after a bad protobuf release (protocolbuffers/protobuf#7827) and a near miss with Guava (google/guava#3994), I figured it was worth bringing this up again in case you want to take additional measures.
The text was updated successfully, but these errors were encountered: