Robolectric 2.3 support without any Robolectric modifications

[jacobtabak]

This branch pulls up all the private logic from RobolectricTestRunner into BurstRobolectricRunner. Unfortunately, it's only compatible with Robolectric 2.3 right now, but with some minor changes to Robolectric (next major version) we could easily remove most of the logic from BurstRobolectricRunner.

[JakeWharton]

This isn't as terrible as I expected. We need to push whatever changes are needed into Robolectric ASAP since I think a release is coming soon.

[jacobtabak]

How to fix this? I don't see a dependency on the support lib anywhere.

[ERROR] Failed to execute goal on project burst-robolectric: Could not resolve dependencies for project com.squareup.burst:burst-robolectric:jar:1.0.1-SNAPSHOT: Could not find artifact com.android.support:support-v4:jar:19.0.1 in central

[JakeWharton]

Ugh, it's transitive from Robolectric. Gross.

[jacobtabak]

Oh I see now.

Robolectric requires the Google APIs for Android (specifically, the maps JAR) and Android support-v4 library

[JakeWharton]

What happens if you add an <exclude> for those transitive deps?

[jacobtabak]

I imagine CI would fail, but can try. Is this the right solution? https://github.com/mosabua/maven-android-sdk-deployer

[JakeWharton]

It's the right solution to fix Robolectric building, but we can't and won't force that on this project.

[jacobtabak]

(CI running) I've never used it before, it's messy? Can it be isolated to this one module?

[jacobtabak]

No luck. Reverting that for now. Any way forward?

[jacobtabak]

Is this a dealbreaker or is it still worth pursuing the changes to robolectric test runner to make it extensible without the duplicated code?

[JakeWharton]

It's still worth pursuing upstream. We can figure out a way to resolve the build here separately.

[dlubarov]

Closing since this is old, but feel free to reopen it if you still want to pursue this.