This will break a lot of scripts that do javadoc, static analysis, etc. which rely on the bootclasspath for a complete picture of the code. I can see at least four occurrences of this in our build (not including inside of any plugins we use).
On Tue Feb 03 2015 at 3:58:09 PM Artem Zinnatullin < [email protected]> wrote: > Hello ADT team, I wanted to try Android Gradle plugin v1.1.0-rc1 because > of Unit tests support, but Kotlin Gradle > plugin 'org.jetbrains.kotlin:kotlin-gradle-plugin:0.10.195' failing the > build because of changes in Android one: > > Execution failed for task ':app:compileDevEnvDebugKotlin'. > > > No signature of method: > com.android.build.gradle.AppPlugin.getBootClasspath() is applicable for > argument types: () values: [] > > Here is the problem in Kotlin Gradle plugin source "link > <https://github.com/JetBrains/kotlin/blob/master/libraries/tools/kotlin-gradle-plugin/src/main/kotlin/org/jetbrains/kotlin/gradle/plugin/android/AndroidGradleWrapper.groovy#L15> > " > > As I see, BasePlugin now doesn't provide getBootClasspath any more. > > What is more correct: return method to BasePlugin or fix Kotlin 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/d/optout. > -- 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.
