What happened: - While we fixed dependencies resolution in the 1.1 plugin, we changed the way we report dependencies on these type of projects from flat (local) jars to actual project dependencies. The way it's reported is technically better/more accurate. This means the Gradle Plugin is technically not broken, but...
- This broke the Gradle/Studio integration, as Studio wasn't designed to handle modules that are just a wrapper over pure local jar/aar files with no Java nor android plugin applied. This was subsequently fixed in Studio 1.2. Xav On Mon, Mar 16, 2015 at 2:57 PM, Greg Macdonald <[email protected]> wrote: > Ah, yes, I see it works with the Canary build. A comment in the release > notes for the plugin could be useful. > > thanks, > greg > > -- > 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.
