The deprecation of Jake's plugin by no means that it can't be maintained by others; there are interested parties apart from Jake himself who could well take on its maintenance.
While I agree with the principle of forcing the Google tools team's hand and encouraging a built-in solution for unit testing, I care enough about maintaining a clean way for my team to use Robolectric that I'm willing to do what I can to make sure the plugin is maintained until something better comes along. Indeed, if it breaks with 0.8.x of the Android Gradle plugin, I'll put in the time to make it work again if there is no better solution. *Avram Lyon* Android wrangler | Scopely, Inc. Refer The Smartest Person You Know And Pocket $5,000! * Learn more: scopely.com/referrals <http://www.scopely.com/referrals/?page=4>* On Thu, Jan 23, 2014 at 1:31 AM, Łukasz Strzelecki <[email protected]>wrote: > 1. Plugin is depricated. And not supported anymore. This plugin works in > SNAPSHOT version. But what happen if plugin for gradle be updated. Then i > can stick with current version of android gradle plugin. Cuz my tests will > not run in newer version of plugin. > 2. Why JUnit testing is so hard? Unit testing is base principal of > checking your code. > > Please add built-in feature for Unit testing like it's in old java plugin. > > -- > 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/groups/opt_out. > -- 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/groups/opt_out.
