add JDK 17 build about community-build HOT 8 CLOSED

2.13.x core is green. I will dig into the specific failures

2.12.x core fails with some lambda deserialization problem. I've opened a separate ticket on it: scala/bug#12419

from community-build.

👍 thank you, this is the perfect time to start testing 17.

from community-build.

this is great! looking forward to start using the newer JVMs.

from community-build.

Jason fixed the deserialization thing, so the 2.12.x core is now green too (on 2.12.15-bin-b2b8816)

from community-build.

2.13.x status as of this run: FAILURES (UNEXPECTED): akka-http,akka-more,macwire,classutil

all four repos are running afoul of https://openjdk.java.net/jeps/403, resulting in java.lang.reflect.InaccessibleObjectExceptions

I will mark them as expected-to-fail.

• macwire: notified maintainers: softwaremill/macwire#162
• classutil: repo seems abandoned
• @patriknw heads up on the akka-http failure and the akka-more failure

I suspect it would be possible for me to make them pass by replacing --illegal-access=... with the more specific --add-opens, but in general, it's not a priority for us to get out ahead of upstream maintainers on JDK 17 support once the overall number of green projects seems adequate for QAing Scala itself.

from community-build.

Thanks @SethTisue .
I have created issues akka/akka-http#3852 and akka/akka#30341

from community-build.

declaring victory here. we'll want to ship 2.12.15 before too much longer, in order to get the serialization fix out

from community-build.

2.12.15 planning thread: https://contributors.scala-lang.org/t/scala-2-12-15-planning/5152

from community-build.