AFAIK this has always been the case, in ADT/Ant/Gradle. However we have changed some things in our dependency management (in Gradle) so this may have changed the order of things.
https://code.google.com/p/android/issues/detail?id=66751 On Thu, Mar 6, 2014 at 4:05 PM, Benjamin Cooley <[email protected]>wrote: > It seems that the newest android plugin version is putting all the add-on > libraries from an add-on onto the classpath, vs just those added with > uses-library in the manifest file. I am pretty sure that some of the > earlier versions of the plugin did not do this. Because add-on libraries > are added to the classpath first, this means you can get a compile time > error if you have an identical class name / package with a different API, > since the library one is always used, even if you do not have > 'uses-library' on that project. > > Is this desired? Seems like you should only add them to the classpath if > it is added in the manifest file. > > - Ben > > -- > 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. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
