luke
/
sbt
mirror of https://github.com/sbt/sbt.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove the use of `BaseIvySpecification` 

This is the proof that we're now testing the Zinc public API because
we're resolving with the ivy options and resolution specified in the
default compiler bridge provider.
This commit is contained in:
jvican 2017-05-20 02:37:16 +02:00
parent 4d0f06a2ee
commit 96f7e08864
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
internal/zinc-ivy-integration/src/test/scala/sbt/internal/inc/BridgeProviderSpecification.scala
View File

@ -18,11 +18,17 @@ import xsbti.{ ComponentProvider, GlobalLock }
/**
* Base class for test suites that must be able to fetch and compile the compiler bridge.
*
* This is a very good example on how to instantiate the compiler bridge provider.
*/
abstract class BridgeProviderSpecification extends BaseIvySpecification {
override def resolvers: Vector[Resolver] =
Vector(ZincComponentCompiler.LocalResolver, DefaultMavenRepository)
private val ivyConfiguration = mkIvyConfiguration(UpdateOptions())
abstract class BridgeProviderSpecification extends UnitSpec {
def currentBase: File = new File(".")
def currentTarget: File = currentBase / "target" / "ivyhome"
def currentManaged: File = currentBase / "target" / "lib_managed"
val resolvers = Array(ZincComponentCompiler.LocalResolver, DefaultMavenRepository)
private val ivyConfiguration =
ZincComponentCompiler.getDefaultConfiguration(currentBase, currentTarget, resolvers, log)
def secondaryCacheDirectory: File = {
val target = file("target").getAbsoluteFile