Mai Huy Hoàng 52ac4e02ee [2.x] fix: hash the boot classpath in a deterministic order (#9809) ...

The launcher enumerates the boot directory, so `AppProvider.mainClasspath` and `ScalaProvider.jars` come back
in filesystem order, and sbt 2 folds that classpath into the metabuild's `CompileInputs2`. Two machines with
identical inputs therefore compute different keys: measured on one project at the same commit, same sbt and
same JDK, 439 classpath entries on both sides, the same set, 83 of them at a different index and all under
${SBT_BOOT}.

Sorting happens after conversion to the rooted virtual path, so the order is independent of the filesystem
and of where the boot directory lives. The order being replaced is a directory listing, not one anybody
chose. `Main.rawEval` builds the same list but never reaches a cache key, so it is left alone.

Generated-by: Claude Opus 5 (Claude Code)

2026-09-22 01:41:59 -04:00

..

src

[2.x] fix: hash the boot classpath in a deterministic order (#9809)

2026-09-22 01:41:59 -04:00

NOTICE

Transfer copyright to Scala Center

2023-06-20 16:39:07 +02:00