sbt, the interactive build tool
-Dsbt.argsfile=false or SBT_ARGSFILE environment variable) #7010 by @easel
buildTarget/outputPaths method of Build Server Protocol. #6985 by @povder
Full Changelog: https://github.com/sbt/sbt/compare/v1.7.1...v1.8.0
-Dsbt.argsfile=false or SBT_ARGSFILE environment variable) #7010 by @easel
buildTarget/outputPaths method of Build Server Protocol. #6985 by @povder
Full Changelog: https://github.com/sbt/sbt/compare/v1.7.1...v1.8.0-RC1
Full Changelog: https://github.com/sbt/sbt/compare/v1.7.2...v1.7.3
See https://github.com/sbt/sbt/releases/tag/v1.7.0 for the details on sbt 1.7.x.
Fixes invalidation of incremental testQuick task #6903 by @gontard
Fixes /tmp/.sbt/ collision for domain socket #7041 by @eed3si9n
Adds workaround for dependencyBrowseGraph with sometimes missing node #6978 by @frosforever
Updates sbt new by default to use Giter8 0.15.0 #7038 by @eed3si9n
Adds diagnosticCode and diagnosticRelatedInforamation (sic) to InterfaceUtil.problem(...) #7006 by @ckipp01
See https://github.com/sbt/sbt/releases/tag/v1.7.0 for the details on sbt 1.7.x.
Full Changelog: https://github.com/sbt/sbt/compare/v1.7.0...v1.7.1
++ is stricter. See below.XDG_RUNTIME_DIR and /tmp #6887 by @AlonsoM45
Resolver.sonatypeRepo and adds Resolver.sonatypeOssRepos, which includes https://s01.oss.sonatype.org/ by @armanbilge in lm#393
++ command updatesPrior to sbt 1.7 ++ <sv> <command1> filtered subprojects using crossScalaVersions having the same ABI suffix as <sv>. This behavior was generally not well understood, and also created incorrect result for Scala 3.x since ++ 3.0.1 test could downgrade subproject that may require 3.1 or above.
sbt 1.7.0 fixes this by requiring ++ <sv> <command1> so <sv> part can be given as a semantic version selector expression, such as 3.1.x or 2.13.x. Note that the expression may match at most one Scala version to switch into. In sbt 1.7.0, a concrete version such as ++ 3.0.1 equires exact version to be present in crossScalaVersion.
This contribution was a collaborated effort among Arnout Engelen #6894, Rui Gonçalves lm#400, and Eugene Yokota.
In zinc#1082, Toshiyuki Takahashi contributed a fix to ignore Problem#rendered passed from the compiler when sbt uses position mapper to transform the position. This is aimed at fixing the error reporting for Play on Scala 3.
In #6874, Chris Kipp extended xsbti.Problem to track richer information available in Scala 3. This is aimed at enhancing the compilation errors reported to BSP client such as Metals.
build/publishDiagnostics in BSP #6847/#6929 by @tanishiking and @kpodsiad
Fixes under-compilation when Java annotation changes by @SethTisue in zinc#1079
Fixes ipcsocket JNI cleanup code deleting empty directories in /tmp ipc#23 by @eed3si9n
Fixes command argument parsing with quotes in -a="b c" pattern #6816 by @Nirvikalpa108
Fixes proxyInputStream#available, which affected sbt-site previewSite #6965 by @eed3si9n
++ is stricter. See below.XDG_RUNTIME_DIR and /tmp #6887 by @AlonsoM45
Resolver.sonatypeRepo and adds Resolver.sonatypeOssRepos, which includes https://s01.oss.sonatype.org/ lm393 by @armanbilge
++ command updatesPrior to sbt 1.7 ++ <sv> <command1> filtered subprojects using crossScalaVersions having the same ABI suffix as <sv>. This behavior was generally not well understood, and also created incorrect result for Scala 3.x since ++ 3.0.1 test could downgrade subproject that may require 3.1 or above.
sbt 1.7.0 fixes this by requiring ++ <sv> <command1> so <sv> part can be given as a semantic version selector expression, such as 3.1.x or 2.13.x. Note that the expression may match at most one Scala version to switch into. In sbt 1.7.0, a concrete version such as ++ 3.0.1 requires exact version to be present in crossScalaVersion.
This contribution was a collaborated effort among Arnout Engelen #6894, Rui Gonçalves lm#400, and Eugene Yokota.
In zinc#1082, Toshiyuki Takahashi contributed a fix to ignore Problem#rendered passed from the compiler when sbt uses position mapper to transform the position. This is aimed at fixing the error reporting for Play on Scala 3.
In #6874, Chris Kipp extended xsbti.Problem to track richer information available in Scala 3. This is aimed at enhancing the compilation errors reported to BSP client such as Metals.
build/publishDiagnostics in BSP #6847/#6929 by @tanishiking and @kpodsiad
XDG_RUNTIME_DIR and /tmp #6887 by @AlonsoM45
Resolver.sonatypeRepo and adds Resolver.sonatypeOssRepos, which includes https://s01.oss.sonatype.org/ lm393 by @armanbilge
++ command updatesPreviously ++ <sv> <command1> filtered subprojects using crossScalaVersions having the same ABI suffix as <sv>. This incorrectly matched subprojects with 3.1.3 when ++ 3.0.1 test is given. sbt 1.7.0 fixes this by requiring ++ <sv> <command1> to be backward compatible. Rui Gonçalves contributed this fix as lm#400.
In #6894, Arnout Engelen contributed expansion to ++ <sv> <command1> so <sv> part can be given as a semantic version selector expression, such as 2.13.x. Note that the expression may match at most one Scala version to switch into.
In zinc#1082, Toshiyuki Takahashi contributed a fix to ignore Problem#rendered passed from the compiler when sbt uses position mapper to transform the position. This is aimed at fixing the error reporting for Play on Scala 3.
In #6874, Chris Kipp extended xsbti.Problem to track richer information available in Scala 3. This is aimed at enhancing the compilation errors reported to BSP client such as Metals.
build/publishDiagnostics in BSP #6847 by @tanishiking
/tmp ipc#23 by @eed3si9n
-a="b c" pattern #6816 by @Nirvikalpa108
ThisBuild / includePluginResolvers #6849 by @bjaglin
Full Changelog: https://github.com/sbt/sbt/compare/v1.6.2...v1.7.0-RC1
XDG_RUNTIME_DIR and /tmp #6887 by @AlonsoM45
Resolver.sonatypeRepo and adds Resolver.sonatypeOssRepos, which includes https://s01.oss.sonatype.org/ lm393 by @armanbilge
In zinc#1082, Toshiyuki Takahashi contributed a fix to ignore Problem#rendered passed from the compiler when sbt uses position mapper to transform the position. This is aimed at fixing the error reporting for Play on Scala 3.
In #6874, Chris Kipp extended xsbti.Problem to track richer information available in Scala 3. This is aimed at enhancing the compilation errors reported to BSP client such as Metals.
build/publishDiagnostics in BSP #6847 by @tanishiking
-a="b c" pattern #6816 by @Nirvikalpa108
ThisBuild / includePluginResolvers #6849 by @bjaglin
Full Changelog: https://github.com/sbt/sbt/compare/v1.6.2...v1.7.0-M3
sbt 1.7.0 implements support for Scala 3.1.2's improved forward compatibility feature.
ThisBuild / scalaVersion := "3.1.2"
ThisBuild / scalaOutputVersion := "3.0.2"
This sets the -scala-output-version compiler option to 3.0, which lets us generate TASTy files and bytecode compatible with older Scala 3.x versions, while using newer Scala 3.x compiler at runtime. In addition, runtime Scala version and POM entries are also downgraded to 3.0.2.
The sbt support for this was contributed by Michał Pałka at VirtusLab as #6814.
In zinc#1082, Toshiyuki Takahashi contributed a fix to ignore Problem#rendered passed from the compiler when sbt uses position mapper to transform the position. This is aimed at fixing the error reporting for Play on Scala 3.
In #6874, Chris Kipp extended xsbti.Problem to track richer information available in Scala 3. This is aimed at enhancing the compilation errors reported to BSP client such as Metals.
build/publishDiagnostics in BSP #6847 by @tanishiking
-a="b c" pattern #6816 by @Nirvikalpa108
ThisBuild / includePluginResolvers #6849 by @bjaglin
Full Changelog: https://github.com/sbt/sbt/compare/v1.6.2...v1.7.0-M2