Support building with SBT pre- and post- 0.13.1 about sbt-extras

[paulp]

Using the latest jar is what it used to do. We ran into issues like sbt/sbt#986 which falsify the claim that you can use the latest launcher on earlier versions - the change in the jline version is not the only example.

[ms-tg]

Thanks for clarifying, @paulp.

Would you please re-open this issue, but without presuming the solution above? I hope you can help us to work with us, and Typesafe, to identify the best way forwards to resolve it.

Specifically, can you confirm that the -no-shared option does not, in fact, fix this behavior?

Steps to reproduce:

1. Build an SBT 0.12.x project using sbt-extras
2. Build an SBT 0.13.5 project using sbt-extras -no-shared

We would have expected success via this workaround for the ivy version format issue; instead, we are still seeing failures with "No scala version specified".

NOTE: It's very possible we are doing something else wrong, which is why we really want external confirmation of a reproducing this scenario.

Thanks so much for all your work!

/CC @ashtonhepburn @flicken @Grundlefleck

[paulp]

I'm in amish country, literally, enjoying the internet over a straw. -no-share is out of my reach as it downloads the internet. However I can't verify that action X does or doesn't fix behavior Y when I never see behavior Y in the first place. I build all kinds of projects using all kinds of sbt versions, necessarily implying flipping around between versions definitely including 0.12.x versions. I have never to my recollection seen the "No scala version specified" message.