On 27/09/2013, at 4:24 AM, Alex Ruiz <alr...@google.com> wrote: > Greetings, > > * Introduction > Some Android Studio users have reported that it is not possible to compile a > project with AIDL files with Gradle 1.8, but the same project compiles fine > with Gradle 1.6 and 1.7. Here is the ticket: > https://code.google.com/p/android/issues/detail?id=60433 > > * What I found > After digging into the code of our Android Gradle plug-in and with an insane > amount of luck (I'm fairly new to this code) I was able to fix our plug-in by > making some dependencies explicit. Let me explain: > > - Project compilation was failing with a MethodNotFoundException, which was > pretty weird. > > - The project that had the failing code is 'gradle' (that's the name of our > project.) It depends on the project 'builder'. 'builder' declares these > dependencies: > compile "com.android.tools:sdklib:$project.ext.baseAndroidVersion" > compile "com.android.tools:sdk-common:$project.ext.baseAndroidVersion" > compile "com.android.tools:common:$project.ext.baseAndroidVersion" > > - To fix this bug, I had to add these dependencies to 'gradle' project. I > thought that 'gradle' would get them from 'builder' automagically (seems to > be the case for Gradle 1.7) > > * Question > (Please bear with me because I'm fairly new to all this) > Is this change of behavior intended? I apologize in advance if this was > discussed or communicated in the past and I missed it.
There should not be any changes in behaviour. Which version of the Android plugin is the problem happening with? -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com Join us at the Gradle eXchange 2013, Oct 28th in London, UK: http://skillsmatter.com/event/java-jee/gradle-exchange-2013
