add JDK 23 to build tool table

[SethTisue]

@eed3si9n what should I put for sbt?

@lefou what should I put for mill?

@Gedochao should I add a scala-cli column?

[eed3si9n]

We only run CI tests on JDK 17 (https://www.scala-sbt.org/1.x/docs/Setup.html). If anything later worked, it's purely by lucky accident, but people are free to choose whatever.

[Friendseeker]

@eed3si9n

For sbt, would it be an improvement to add CI tests for all combination of major OS (Ubuntu, Mac, Windows) & LTS Java version?

I use sbt with Java 21 locally and can confirm it works quite well. Some minor change in ci.yml to declare a testing matrix would do it (which I can work on).

Even if some of the newly added tests fail, given the massive userbase of sbt, the CI failures would likely be real issue that needs to be addressed.

[eed3si9n]

@Friendseeker

For sbt, would it be an improvement to add CI tests for all combination of major OS (Ubuntu, Mac, Windows) & LTS Java version?

I've created sbt/sbt#7731. Let's discuss there.

[SethTisue]

for the purposes of this web page, it's enough that there isn't some obvious showstopper that most people will hit — particularly since 23 isn't LTS

[SethTisue]

@lefou what should I put for mill?

[lefou]

Mill has no dedicated Java 23 test suite. Our full CI doesn't succeed on Java 23 due to some tests exercising older Scala versions that are known to be incompatible with Java 21 and above. But Mill 0.11.11 runs with Java 23 without known issues. I guess older versions down to 0.11.5 might work as well.

[lefou]

I just checked, I can build Mill's own code base (0.11.x branch) with Mill 0.11.8 on Java 23 too. I couldn't check older versions due to feature requirements in that project.

[SethTisue]

thank you @lefou

leaving as draft until we hear from Piotr (there's no big rush)