By Eugene Yokota (@eed3si9n) March 26, 2018
Hi everyone. It’s been a while since the last 1.1.x hotfix, so here’s 1.1.2.
As a reminder, sbt 1 is released under Semantic Versioning. So plugins released for 1.0.x will continue to work throughout 1.x including 1.1, 1.2, etc. This includes the latest 1.1.2 as well.
- Fixes triggered execution’s resource leak by caching the watch service. #3999 by @eatkins
- Fixes classloader inheriting the dependencies of Scala compiler during
runzinc#505 by @eed3si9n
- Fixes forked test concurrency issue. #4030 by @eatkins
newcommand leaving behind target directory #4033 by @eed3si9n
- Fixes handling on null Content-Type. lm214 by @staale
- Fixes null handling of
ivySettingsfile. lm#218 by @IanGabes
sbt.boot.lockas a JVM property to opt-out of locking. #3927 by @dwijnand
SBT_GLOBAL_SERVER_DIRenv var as a workaround to long socket file path on UNIX. #3932 by @dwijnand
- Fixes forked runs reporting noisy “Stream closed” exception. #3970 by @retronym
- Fixes test compilation not getting included in VS Code save trigger. #4022 by @tmiyamon
- Fixes sbt server responding with string id when number id passed. #4025 by @tiqwab
getDecoderin Analysis format zinc#502 by @jilen
- Fixes equal / hashCode inconsistencies around Array. zinc#513 by @eed3si9n
java9-rt-ext-outputin rt export process lp#211 by @eatkins
- Fixes JDK version detection for Java 10 friendliness. lp#219 by @eed3si9n and @2m
- Fixes quoting in Windows bat file. lp#220 by @ForNeVeR
-errornot suppressing startup logs. #4036 by @eed3si9n
- Performance optimization around logging. util#152 by @retronym
- Performance fix by caching the hashCode of
Configuration. lm#213 by @retronym
- Returns error code
-33000Lon sbt server when a command fails. #3991 by @dwijnand
- Allows wildcards in organization and artifact. #215 by @dhs3000
- Updates to latest Jsch to support stronger key exchange algorithms. lm#217 by @ryandbair
- Fixes preloading of compiler bridge. lp#222 by @analytically
- Updates contribution guide. #3960/#4019 by @eed3si9n and @itohiro73
buildinfo.BuildInfofrom sbt main that was intended for testing. 3967 by @dwijnand and @xuwei-k
- Various improvements around Zinc benchmark by @retronym
I participated in ScalaMatsuri 2018 OSS Hackathon as one of maintainers on March 16th:
Five first-time contributors were assigned for sbt. First we went through the contribution guide so everyone can build sbt from source. Next, we picked out a task for each person from the “help wanted” issue list. During the next few hours, the contributors went through reproducing bugs, updating documentation, and fixing bugs. One of the interesting pull request that came out of it was an update to the contribution guide. #4019 Another was a bug fix on sbt server.
It was a fun experience for me, and I hope some of the participants would continue to contribute to the free/libre/opensource ecosystem going forward as well.
An area that is getting our attention recently is improving the performance. We would like to thank Scala team’s Jason Zaugg and Akka team’s Johannes Rudolph for sending in PRs. Some of the performance fixes went into 1.1.2; while we are studying and continuing the research for for 1.2.x.
A huge thank you 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.
sbt 1.1.2 was brought to you by 23 contributors, according to
git shortlog -sn --no-merges v1.1.1...v1.1.2 on sbt, zinc, librarymanagement, util, io, launcher-packege, and website: Dale Wijnand, Eugene Yokota, Jason Zaugg, Kenji Yoshida (xuwei-k), Ethan Atkins, Martijn Hoekstra, Martynas Mickevičius, Dennis Hörsch, Hosam Aly, Antonio Cunei, Friedrich von Never, Hiroshi Ito, Ian Gabes, Jilen Zhang, Mathias Bogaert, Naohisa Murakami (tiqwab), Philippus Baalman, Ryan Bair, Seth Tisue, Ståle Undheim, Takuya Miyamoto (tmiyamon), Yasuhiro Tatsuno. Thank you!
For anyone interested in helping sbt, there are many avenues you could help, depending on your interest.
- Migrate library builds to sbt 1, or update plugins.
- Report bugs when you see them.
- Send in fixes to bugs.
- Update documentation.