From 1150ece77a15fb45e9de78ecfded4090b330a747 Mon Sep 17 00:00:00 2001 From: Anatolii Kmetiuk Date: Wed, 3 Dec 2025 11:21:04 +0900 Subject: [PATCH] Fix #8341: Create Migration Guide file --- MIGRATION.md | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 MIGRATION.md diff --git a/MIGRATION.md b/MIGRATION.md new file mode 100644 index 000000000..1a5e77539 --- /dev/null +++ b/MIGRATION.md @@ -0,0 +1,9 @@ +# Migration Guide from sbt 1 to sbt 2 + +In principle, migrating your build from sbt 1 to sbt 2 should be a matter of updating the sbt version in `build.properties`. However, there are some changes in behavior that you may need to account for. + +This document will outline possible changes in behavior that affect your build when migrating from sbt 1 to sbt 2. Implement them in case out-of-the-box migration does not work. + +## Changes in behavior + +- `exportJars` defaults to `true`, was `false`. This might break `getResource("/")` and `resource.toURI`. Set `exportJars := false` if this logic is broken in your build, producing `NullPointerException`s and `FileSystemNotFoundException`s. Set `exportJars := false` in your build if you want to keep the old behavior. The change was introduced by [sbt/sbt#7464](https://github.com/sbt/sbt/pull/7464), see also [blog](https://eed3si9n.com/sbt-remote-cache/).