Failing tests in `integration.manual[migrating]` module

Open ajaychandran opened this issue 1 month ago • 2 comments

The following tests are failing due to a mismatch in tooling compatibility:

MillInitSbtScalaLoggingTests
MillInitSbtScoptTests

The issue can be fixed by using ~~a Java home based on the SBT version used in the project~~ the system JDK to run the sbt shell.

MillInitSbtScalaPBTests is also failing. The underlying issue here is that a build file is generated for an invalid path. The project uses sbt-projectmatrix plugin that is not supported by the conversion. It is preferable to fail fast in this case, instead of generating incorrect build files.

Oct 28 '25 16:10 ajaychandran

@ajaychandran How can we tell the sbt importer to use a specific JVM ID?

Oct 28 '25 21:10 lefou

@ajaychandran How can we tell the sbt importer to use a specific JVM ID?

By passing the -java-home command line option to sbt. For real world usage, the best option is using the system JDK. We already do this for the Gradle conversion where gradle-jvm-id option defaults to system and is overridden in tests.

Oct 28 '25 21:10 ajaychandran