replacement launcher for 0.11.3 (and earlier)

[Mark Harrah]

I've published what should be a drop-in replacement for the 0.11.3 launcher[1]. This launcher should be able to launch any version of sbt (back to 0.7) according to the sbt.version specified in project/build.properties. It will default to 0.11.3 if no project/build.properties exists.

This retroactively fixes scala-tools issues for the launcher (when retrieving Scala or sbt) for the supported versions, but it cannot change the default resolvers used for a build. For builds that wish to continue to use older versions of sbt, override externalResolvers to exclude scala-tools[2].

Once again, if users can test and confirm this works, we'll link to this launcher instead of the original 0.11.3 launcher.

Thanks,
Mark

[1] http://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/sbt-launch/0.11.3-2/sbt-launch.jar
[2] For 0.10+,

externalResolvers <<= resolvers map { rs =>
Resolver.withDefaultResolvers(rs, mavenCentral = true, scalaTools = false)
}

[dave]

Excellent! One launcher to rule them all. This will make life much simpler.

Will future launchers also be backward compatible? That would greatly help those times when we have to dig into old code that uses older versions of sbt.

dave

[Mark Harrah]

Hi Dave,

On Tue, 29 May 2012 07:48:39 -0700 (PDT)
dave <leed...@yahoo.com> wrote:

> Excellent! One launcher to rule them all. This will make life much simpler.
>
> Will future launchers also be backward compatible? That would greatly help
> those times when we have to dig into old code that uses older versions of
> sbt.

Yes, that is the idea.

Note that the launcher code itself has always been backward compatible. If you give the 0.11.3 launcher the configuration file for 0.7.7, it should launch it ok. The problem has been the default configuration file has changed and doesn't work with different versions. This latest change allows different configuration files to be used as appropriate.

-Mark