eugene yokota

@avdv Would putting the following in `project/plugins.sbt` mitigate the issue you're seeing?: ```scala scalaVersion := "2.12.4" ```

I am looking at: - https://github.com/sbt/sbt/compare/v1.1.4...v1.1.5 - https://github.com/sbt/zinc/compare/v1.1.5...v1.1.7 - https://github.com/sbt/io/compare/v1.1.6...v1.1.8 but nothing is jumping at me. In terms of the metaspace and tests https://github.com/sbt/sbt/pull/4114 sounds related, but it was supposed...

I've been using https://github.com/sbt/librarymanagement, and running: ``` > testOnly sbt.internal.librarymanagement.EvictionWarningSpec ``` each time, I do see metaspace increase.

If we are leaking classloader in TestFramework.scala, it has to have been happening for a while since the history doesn't show much https://github.com/sbt/sbt/commits/1.x/testing/src/main/scala/sbt/TestFramework.scala

omg. Thanks @retronym! These are all helpful info.

Not a bug. As the title suggests, the error message needs to improve.

Pushed a tag - https://github.com/sbt/flyway-sbt/releases/tag/v11.11.0

There were similar issue for JLine and REPL: https://github.com/scala/scala3/issues/22756

@SethTisue > is there an open question of whether sbt 2 final release will adopt Scala 3.8? because then sbt 2 would require JDK 17 (but people could still target...

Yea, if people are ok with it, I can actually start a library and maybe build this feature into sbt itself?