Library shell gives you JDK 8, but some tooling requires JDK 11+

[armanbilge]

mdoc recently dropped support for JDK 8, so it's no longer possible to build documentation sites in the library shell.

• Java 8 in CI: the end is nigh sbt-typelevel#215 (comment)

[rossabaker]

I think "library" is not a name that aged well, since different projects have different requirements, and the world wasn't ever going to cut it off at once.

Maybe we should just provide an 8, 11, 17, and 21 and phase out "application" and "library".

[rossabaker]

But that doesn't capture the different defaults of the non-JDK platforms. Drat. It's nice to have a one liner to drop in a command line or private .envrc.

[armanbilge]

I think "library" is not a name that aged well,

Another complaint I had with the current "library" shell is that while it is reasonable for CI to run on JDK8, for local dev I'd typically prefer a fast, modern JVM i.e. 17+ and only "drop down" to JDK 8 if CI catches something weird.

[zarthross]

#192 should have improved the issue, at least in regards to metals and scala-cli, but this is probably still needs further thought to fully address.