Hi Mike, I actually jumped on your plugin as soon as you resumed it from Jake's one. However, at the time I needed to be on latest android plugin and yours was not yet on par, so I went back to the other one.
Right now I am not doing the jump again because the old plugin still works (changing 2 lines), and my project prefers I spend time on other tasks until our tests won't break or there is (this or another) plugin that could be called "final". Maybe I could do it if I find some spare time, if curiosity wins :p On Fri, May 9, 2014 at 4:39 PM, Mike Grafton <[email protected]> wrote: > Hey Diego - > > Just wondering if you were able to give the robolectric fork a try, and if > it didn't work, why. If something went wrong please post an > issue<https://github.com/robolectric/gradle-android-test-plugin/issues>or > join the discussion on the robolectric > list <https://groups.google.com/forum/#!forum/robolectric>. Thanks a > bunch! > > Mike > > > On Thu, May 8, 2014 at 10:51 PM, Diego Costantini < > [email protected]> wrote: > >> For now I published my fixed fork in sonatype, minimum effort until a >> proper official solution is out ;) >> >> Sent from my Nexus 4 >> On May 9, 2014 12:01 AM, "Felipe Lima" <[email protected]> wrote: >> >>> Diego, >>> >>> You can use the robolectric fork of the project which is now the most up >>> to date: >>> >>> classpath 'org.robolectric.gradle:gradle-android-test-plugin:0.10.+' >>> >>> On Friday, May 2, 2014 12:28:13 PM UTC-3, Diego Costantini wrote: >>>> >>>> Already made a pull request, just in case that guy would be so gentle >>>> to publish on sonatype 0.10 snapshot of his deprecated plugin :p >>>> >>>> >>>> On Fri, May 2, 2014 at 5:24 PM, Jake Wharton <[email protected]>wrote: >>>> >>>>> On Fri, May 2, 2014 at 4:43 AM, Diego Costantini < >>>>> [email protected]> wrote: >>>>> >>>>>> I am afraid it might have something to do with the deprecated unit >>>>>> tests plugin from Jake Wharton, but before despairing for the lack of >>>>>> support, better be sure that is the case. >>>>>> >>>>> >>>>> It is the case. >>>>> >>>>> -- >>>>> You received this message because you are subscribed to a topic in the >>>>> Google Groups "adt-dev" group. >>>>> To unsubscribe from this topic, visit https://groups.google.com/d/ >>>>> topic/adt-dev/mCDff9Sl9-s/unsubscribe. >>>>> To unsubscribe from this group and all its topics, send an email to >>>>> [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "adt-dev" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/adt-dev/mCDff9Sl9-s/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "adt-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to a topic in the > Google Groups "adt-dev" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/adt-dev/mCDff9Sl9-s/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
