1.1 already takes care of all of this but in a different way. We are not putting android.jar in MavenCentral, so we're not going to do it for the custom version either. Instead we dynamically generate it on-demand when you use unit testing. Later we will allowing either letting the current method throw exception or remove them.
The issue is that you cannot do 4 because you cannot create a jar/aar that was compiled against this custom android.jar. We'll find a solution for 1.2 On Wed, Feb 4, 2015 at 11:02 AM, Artem Zinnatullin < artem.zinnatul...@gmail.com> wrote: > I think Jake is talking about "finals" free version of android.jar to > allow mocking any class you need. > > What I can suggest: > > 1) Allow to set custom android.jar for test scope via Android Gradle > Plugin, better smtng like this: testCompile > 'com.android:test-android-platform:21.0.0' you got the Idea, just normal > dependency > > 2) Generate and compile version of android.jar with erased "final" > modifyers for each Android platform version and pusblish them to > mavenCentral/jCenter, erasing "final" will allow to use Mockito/etc > libraries for mocking EVERY class you need > > 3) Happy unit testing! > > 4) Community will produce cool mock libraries for different purposes which > you will able to use with required android.jar > > -- > 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 adt-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. http://developer.android.com | http://tools.android.com Please do not send me questions directly. Thanks! -- 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 adt-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
