Migrate to using the sbt/launcher module, rather than having the code embedded.

* Remove launch/* code/tests, as these are in the sbt/launcher project.
* Create a new project which will resolve launcher module from sonatype-snapshots,
  and repackage it for the currently building version of sbt.
* Remove ComponentManagerTest which was relying DIRECTLY on launcher classes.
  We'll need to reconfigure this shortly to enable the tests again.

Remaining TODOs -

* Update resolvers so people can find the launcher.
* Add ComponentManagerTest back.
* Re-publish the sbt-launch.jar in the location it used to be published.
This commit is contained in:
Josh Suereth 2015-03-24 16:12:51 -04:00
parent 2c236de02a
commit df959cf0d4
1 changed files with 6 additions and 0 deletions

View File

@ -7,6 +7,11 @@ import IO.{ createDirectory, delete, touch, withTemporaryDirectory }
import org.apache.ivy.util.ChecksumHelper
import IfMissing.Fail
// TODO - We need to re-enable this test. Right now, we dont' have a "stub" launcher for this.
// This is testing something which uses a launcher interface, but was grabbing the underlying class directly
// when it really should, instead, be stubbing out the underyling class.
/*
object ComponentManagerTest extends Specification {
val TestID = "manager-test"
"Component manager" should {
@ -87,3 +92,4 @@ object ComponentManagerTest extends Specification {
}
}
}
*/