You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we support Java 8 for compilation. Java 8 was released in 2014 and was superseded by Java 11 in 2018. Continuing to support it imposes constraints: relatively trivial ones like avoiding var and certain newer APIs, but also more serious ones like not being able to reference module APIs except through reflection.
We should drop Java 8 support and require a compiler that is at least Java 11. Users will still be able to compile into Java 8 classfiles with --release 8. (They can even use --release 7.)
The text was updated successfully, but these errors were encountered:
I don't think I'd actually want to convince you not to do this, but one note: Various of our projects currently rely on building+testing with Java 8 as an easy (and incomplete...) test of Java 8 compatibility. There are apparently better ways to do that, and we'd like to use Java 11 for the reasons you've mentioned, anyway. So we really should change someday. A bump in Auto's Java requirement would just give us a push in that direction, at least for projects that use it (e.g., Truth).
It's very likely that others are doing similar things, and some of them may or may not complain. I look forward to hearing how it goes without having to be on the direct receiving end of any of those complaints ;)
Currently we support Java 8 for compilation. Java 8 was released in 2014 and was superseded by Java 11 in 2018. Continuing to support it imposes constraints: relatively trivial ones like avoiding
var
and certain newer APIs, but also more serious ones like not being able to reference module APIs except through reflection.We should drop Java 8 support and require a compiler that is at least Java 11. Users will still be able to compile into Java 8 classfiles with
--release 8
. (They can even use--release 7
.)The text was updated successfully, but these errors were encountered: