Matthias Kurz

Oh and you see I build scala-steward locally on commit 083ed690 which basically is latest version 0.34.0

Needs further investigation: - https://docs.jboss.org/hibernate/orm/7.0/migration-guide/migration-guide.html#validator-integration-auto - https://www.playframework.com/documentation/3.0.x/JavaJPA#Bean-Validation-Not-Currently-Supported-in-Play-2.9 - https://docs.jboss.org/hibernate/validator/9.0/reference/en-US/html_single/#validator-gettingstarted-uel

Waiting for a reply in - https://github.com/sbt/sbt-git/pull/243/files#r1804523359 to see if we need to set ```sbt ThisBuild / com.github.sbt.git.SbtGit.GitKeys.useConsoleForROGit := false ``` in `build.sbt`

@jodersky Can you please rebase?

How can the failing tests be fixed? ``` $ grep -r --exclude-dir=.git --exclude-dir=target '2\.13\.1' internal/zinc-benchmarks/src/test/scala/xsbt/ZincBenchmark.scala: val scalaVersion = "2.13.18" internal/compiler-bridge-test/src/test/scala/sbt/internal/inc/CompilingSpecification.scala: def scala213 = "2.13.18" project/Dependencies.scala: val scala213 = "2.13.18" project/Dependencies.scala:...

@mzuehlke yes, it still works. I also mentioned it in my initial post. However it does not write json.

@Friendseeker Not sure if you are aware but you can already call ```sbt dependencyTree/toFile /some/folder/output.txt ``` Also you can override the file with `-f` (force): ```sbt dependencyTree/toFile /some/folder/output.txt -f ```

I am wondering if the `--toFile=` is still needed if you now by default always write the file in the target folder anyway. Reason is because if you have multi-project...

Also, thinking about the `--config` flag: Would it make sense to name file `dependencies-scope.xx` (or `dependencies-Scope.xx`)? Or keep `dependencies.xx` for Compile but add the scope to the file name for...

Yeah, sure, we should just stick with the current way of selecting the scope. It seems I got a bit of tunnel vision while considering this issue... Eventually, I think...