Matthias Kurz

fyi, the current Play `main` branch drops support for Java 11, so we just upgrade jgit ourselves to avoid all those workarounds in future (I think it will take years...

For the play seed projects, as a workaround I made them avoid querying maven.org: - https://github.com/playframework/play-java-seed.g8/pull/205 - https://github.com/playframework/play-java-seed.g8/pull/204 - https://github.com/playframework/play-scala-seed.g8/pull/280 - https://github.com/playframework/play-scala-seed.g8/pull/281

@mjustin thanks for the report. Would you be able to open a pull request with the updated URL? Thanks!

@SethTisue If you cut a new Scala 2.12.x release, it would be great if that would also already unlock Java 25 by upgrading asm (I hope they cut a new...

> As stated in the [Play framework documentation](https://www.playframework.com/documentation/3.0.x/Highlights29#Guice-Upgraded-to-Version-6), Play will no longer support `javax.inject` after the next major release. Yes that's right, however I will not merge this PR in...

No the repo was not deleted, it was migrated. You are actually commenting in the original repo, just under a new location.

@cchantep whenevery you have time, can you take a look at the error when docs get compiled with Scala 3? ``` [error] -- Error: /home/runner/work/anorm/anorm/docs/manual/working/scalaGuide/main/sql/code/MacroToParameters.scala:60:28 [error] 60 | Macro.toParameters("#", Macro.ParameterProjection("bar",...

> Can we help somehow to move forward a release including `pekko-stream` support? @gaeljw (or whoever wants to help) you could take this pull request as base and try to...

I think without the `-E` option, websocat should definitely reply with an echoed close frame. This is just how things should work. With the `-E` option it might make sense...

> The change only affects the `-E` mode. Why just this mode?