eugene yokota

Thanks for the report.

I'm thinking this can be fixed by forwarding the flag in the following line: https://github.com/sbt/sbt/blob/06816499943044d2aac7be1a7f9397d5ce0e978e/scripted/plugin/src/main/scala/sbt/ScriptedPlugin.scala#L81 I wonder if anyone else might be relying on older semantics.

Maybe `ivy.home` is trying to be consistent with Ivy? I would vote for respecting both with `sbt.ivy.home` having higher precedence.

I guess we can just drop `ivy.home` support and use `sbt.ivy.home` here - https://github.com/sbt/librarymanagement/blob/da6897b8a3d4e08d5cfce9589c18b8ae5bff0641/core/src/main/scala/sbt/librarymanagement/ResolverExtra.scala#L395

> I expected there will be no files access changes between 1.6.1 and 1.7.1 versions. This was documented in https://github.com/sbt/sbt/releases/tag/v1.7.0. We do make breaking changes in minor versions.

Commented on https://github.com/scala/bug/issues/12632#issuecomment-1209906363 Yea. Unless something prevents us from going to Scala 3, sbt 2.x should be on 3 (see https://eed3si9n.com/sudori-part3/ etc).

> @eed3si9n do you have any timeline on when you'd like to get 1.8.x out? I don't think we are waiting on anything, so we could potentially ship RC-1 as...

I am guessing that in some situations sbt-coursier's Scala version (2.12.17) is bubbling up. I've opened https://github.com/coursier/coursier/issues/2573 to request 2.12.16 version of sbt-coursier for 1.7.x branch.

@charpov Thanks for the report. Is specific Scala version required to reproduce this behavior?

Thanks for the report. To supplement this, here's what happens without cross building as a reference. ```scala ThisBuild / scalaVersion := "2.13.4" ThisBuild / version := "0.1.0-SNAPSHOT" ThisBuild / organization...