You could build a project that uses Robolectric on a machine that can access a remote repo and then transfer the artifacts from that machines local Maven repo to the local Maven repo on the machine that hosts your project. Be sure both projects use the same version of Android as that will affect which artifacts Robolectric looks for.
--
You received this message because you are subscribed to the Google Groups "Robolectric" group.
To unsubscribe from this group and stop receiving emails from it, send an email to robolectric...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I implemented it as custom ClasspathDependencyLocator used by custom RobolectricTestRunner .
Any chance to push changes in upstream?
Unfortunately I don't know how to pass system.properties from AndroidStudio launcher to test runner with zero-conf, so
generated_org.robolectric.Config.properties is produced by my plugin and used later by IdeAwareRobolectricTestRunner.
Actually the main blocker for single org.robolectric.Config.properties on classpath is relative nature of android.assets\resources\manifest properties (are prepended by './').
I'd like to implement it in a way acceptable for robolectric team team.
Please contact me personally or let's discuss it in https://groups.google.com/forum/#!topic/robolectric/Eg1drYGSMAs .
P.S. testing (including configuration process) should be painless as much as possible.
Thanks.
Bademus
--
--
You received this message because you are subscribed to a topic in the Google Groups "Robolectric" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/robolectric/nJgHtdbkpi8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to robolectric...@googlegroups.com.