If you find any issues with sbt 1.0.0-M5, please report on Github issue.
-sbt team
Anton Kulaga
unread,
Apr 20, 2017, 3:55:17 AM4/20/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to sbt-dev
You mentioned "Some more ambitious aspects of plans for 1.0 have been postponed or scaled back to make 1.0 achievable soon. (For example, cached compilation and replacing Ivy)".
But why was it pushed back? There is a better alternative to ivy, called coursier ( https://github.com/coursier/coursier ), you can just get rid of ivy and put cousier inside by default.
Seth Tisue
unread,
Apr 20, 2017, 11:07:44 AM4/20/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to sbt-dev
On Thu, Apr 20, 2017 at 2:55 AM, Anton Kulaga <anton...@gmail.com> wrote:
> You mentioned "Some more ambitious aspects of plans for 1.0 have been > postponed or scaled back to make 1.0 achievable soon. (For example, cached > compilation and replacing Ivy)". > > But why was it pushed back?
Because it's not easy, so including it in the first 1.0 release would delay the 1.0 release date. The goal is to avoid further delays and get on Scala 2.12 as soon as possible.
> There is a better alternative to ivy, called coursier ( > https://github.com/coursier/coursier ), you can just get rid of ivy and > put cousier inside by default.
Everyone wants this to happen but pushing the change through is not going to be quick or simple. See https://github.com/sbt/sbt/issues/2997 and linked issues. Let's get 1.0 out the door first.