I'm having an issue with upgrading to gradle 1.9 or 1.10 with newer Android
gradle plugin (greater than 0.6).
In my existing project config using Gradle 1.8 and Android Gradle plugin
0.6, here is my build.gradle configuration for my APK (the parent
build.gradle contains the Android gradle plugin version 0.6 dependency):
---
apply plugin: 'android'
repositories {
mavenLocal()
mavenCentral()
}
android {
compileSdkVersion 17
buildToolsVersion "17.0.0"
defaultConfig {
minSdkVersion 16
targetSdkVersion 17
}
}
dependencies {
compile 'com.clover:common:31-SNAPSHOT'
compile 'com.clover:core:14-SNAPSHOT'
}
---
The dependency 'com.clover:common' is installed into my local Maven
repository (~/.m2/repository)
When running '/usr/local/Cellar/gradle/1.8/libexec/bin/gradle dependencies'
I get the following output:
compile - Classpath for compiling the main sources.
+--- com.clover:common:31-SNAPSHOT
| +--- com.clover:common-instrumentation:31-SNAPSHOT
| +--- com.fasterxml.jackson.core:jackson-databind:2.2.3
| | +--- com.fasterxml.jackson.core:jackson-annotations:2.2.3
| | \--- com.fasterxml.jackson.core:jackson-core:2.2.3
| +--- com.fasterxml.jackson.core:jackson-core:2.2.3
| +--- com.clover:core:14-SNAPSHOT
| +--- com.clover.sdk:clover-android-sdk:8-SNAPSHOT
| +--- com.clover:common-style:31-SNAPSHOT
| \--- com.fasterxml.jackson.core:jackson-annotations:2.2.3
+--- com.clover:core:14-SNAPSHOT
When updating my APK build.gradle to point to Gradle plugin 0.8 and build
tools 19.0.1 using gradle 1.10 (and updating the AAR dependencies to add
the '@aar' classifier to the dependency names), I get the following from
'gradle dependencies':
compile - Classpath for compiling the main sources.
+--- com.clover:common:31-SNAPSHOT
+--- com.clover:core:14-SNAPSHOT
So, it seems with some combination of the newer Gradle versions and the new
Android gradle plugin, the transitive dependencies of my .AAR project are
not picked up any longer. I know it's not an issue with the dependency
published in ~/.m2/repository because I'm running the commands above
literally back-to-back with two slight variations of the same repository
with the exact same dependency.
Any one else seen this issue? I was going to start debugging within the
Android gradle plugin if there aren't any known fixes for the above issue.
Thanks,
Duane
--
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/groups/opt_out.
