1.3.2

Fixes with compatibility implication

• sbt launcher script drops -XX:+UseParallelGC for JDK 9 and up since it could cause severe GC pauses given a large heap sbt/sbt-launcher-package#282 / #5045 by @eed3si9n
• Updates to lm-coursier-shaded 2.0.0-RC3-4, which fixes the handling of Basic auth.

Other fixes

• Updates to Scala 2.12.10
• Fixes NoClassDefFoundError at the end of run when thread keeps running after the task. Use allowZombieClassLoaders := true to opt into using classes after the task. #5081 / #5083 by @eatkins
• Adds a new setting called includePluginResolvers (default false).
  When set to true, the project will include resolvers from the metabuild. #5094 by @eed3si9n
• Fixes -v always being on in 1.3.1 - sbt/sbt-launcher-package#283 by @eed3si9n
• Fixes quotation in sbt script - sbt/sbt-launcher-package#280 by @kingslef
• Fixes dashes in sbt script - sbt/sbt-launcher-package#281 by @anilkumarmyla
• Fixes file watching when -Dsbt.global.base is set to a relative path #5048 by @yamachu
• Fixes duplicates in allJars when creating a ScalaInstance #5053 by @unkarjedy
• Fixes deprecation warnings for watch related changes #5054 by @eatkins
• Fixes super shell interfering with consoleQuick and state #5087 by @eatkins
• Fixes build source watch not tracking subproject *.sbt files #5086 by @eatkins
• Fixes race condition around task logging #5069 by @eatkins
• Fixes acquiring timestamp from files with long path name on Windows sbt/io#271 by @eatkins

Participation

sbt 1.3.2 was brought to you by 7 contributors. Ethan Atkins, Eugene Yokota (eed3si9n), Anil Kumar Myla, Dmitrii Naumenko, Kenji Yoshida (xuwei-k), Yusuke Yamada, and Tuomas Lappeteläinen. Thank you!

Thanks to everyone who's helped improve sbt and Zinc 1 by using them, reporting bugs, improving our documentation, porting builds, porting plugins, and submitting and reviewing pull requests.

For anyone interested in helping sbt, there are many avenues for you to help, depending on your interest. If you're interested, Contributing, "help wanted", "good first issue" are good starting points. If you have ideas, come talk to us on sbt-contrib or on Lightbend Discuss