Request for feedback: sbt 1.2.0 roadmap


#21

Agree. For me SBT 1.x is unusable due to performance regression.


#22

What about some love for strict aggregation.


#23

IMO fixing the performance regression and the sbt-maven-resolver should be a priority.

I’d argue that the current support of Maven publishing in SBT 1.x is far from ideal (https://github.com/sbt/sbt/issues/3486). Maintainers of Java/Maven codebases that want to migrate to Scala and setup a diverse release process using SBT cannot do it with SBT 1.x.


#24

Performance. Upgrading from 0.13.15 to 1.0.x or 1.1.0 results in compilation speed taking 30% longer. IMO this should be considered of the highest priority.

I agree. I think the first step is identifying tooling setup needed for core developers and contributors to start measuring / profiling where the hotspots are, and where we regressed.


#25

One first thing you may want to look at: why global plugins are classloaded and initialized in every build.


#26

What’s the difference between ensime-server and sbt-server?


#27

Is this slated for 1.2.0 then?


#28

Yes. We’ve already started addressing some of perf issues in 1.1.2 that was released today - https://developer.lightbend.com/blog/2018-03-26-sbt-1-1-2-hotfix/
and there are active PRs like https://github.com/sbt/sbt/pull/4003


#29

Thanks & great to hear!