If you declare your dependencies with compile 'groupId:artifactId:1.0@aar'
then yes you need to specify transitive=true. as soon as you specify the packaging with @aar, Gradle reverts to not following the transitive dependencies. I'm not sure why. On Mon, Mar 17, 2014 at 9:45 AM, Malachi de AElfweald <[email protected] > wrote: > If it helps any - we are pulling an .aar into Gradle that was published > via Maven. I had to explicitly set transitive=true to resolve the > transitive dependencies. I'm not having Gradle publish anything. > > > On Mon, Mar 17, 2014 at 9:37 AM, Xavier Ducrohet <[email protected]> wrote: > >> I'm following up with the Gradle dev to see what's up. While we have made >> changes in our plugin we are not explicitly removing the dependencies if >> you modify the pom in your build.gradle file, so it looks like we are >> somehow trigger an issue in Gradle. >> >> In the mean time, I'd try to find a way to not modify the pom through the >> Upload task. >> >> >> On Mon, Mar 17, 2014 at 12:50 AM, Renzo Fernando Crisóstomo Medina < >> [email protected]> wrote: >> >>> Yes, I'm publishing these myself with Gradle. I just checked, before the >>> upgrade this was the generated pom: >>> >>> <?xml version="1.0" encoding="UTF-8"?> >>> <project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 >>> http://maven.apache.org/xsd/maven-4.0.0.xsd"; xmlns=" >>> http://maven.apache.org/POM/4.0.0"; >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> >>> <modelVersion>4.0.0</modelVersion> >>> <groupId>no.sysco</groupId> >>> <artifactId>vigiloandroidlibrary</artifactId> >>> <version>1.0.22-SNAPSHOT</version> >>> <packaging>aar</packaging> >>> <name>library</name> >>> <dependencies> >>> <dependency> >>> <groupId>no.sysco</groupId> >>> <artifactId>syscobasecontainer</artifactId> >>> <version>1.2</version> >>> <scope>compile</scope> >>> </dependency> >>> <dependency> >>> <groupId>no.sysco</groupId> >>> <artifactId>syscotouchgallery</artifactId> >>> <version>1.1</version> >>> <scope>compile</scope> >>> </dependency> >>> <dependency> >>> <groupId>com.google.android.gms</groupId> >>> <artifactId>play-services</artifactId> >>> <version>4.2.42</version> >>> <scope>compile</scope> >>> </dependency> >>> </dependencies> >>> </project> >>> >>> But now, it's lacking the transitive dependencies: >>> >>> <?xml version="1.0" encoding="UTF-8"?> >>> <project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 >>> http://maven.apache.org/xsd/maven-4.0.0.xsd"; xmlns=" >>> http://maven.apache.org/POM/4.0.0"; >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> >>> <modelVersion>4.0.0</modelVersion> >>> <groupId>no.sysco</groupId> >>> <artifactId>vigiloandroidlibrary</artifactId> >>> <version>1.0.6</version> >>> <packaging>aar</packaging> >>> <name>library</name> >>> </project> >>> >>> I haven't had a problem with the 0.8 plugin and I haven't upgrade my >>> Gradle installation to 1.11. >>> >>> On Friday, March 14, 2014 9:33:20 AM UTC+1, Renzo Fernando Crisóstomo >>> Medina wrote: >>> >>>> I'm having problems with transitive dependencies since upgrading >>>> to 0.9.+ and 0.5.1. Is anyone having the same issue? I had solved this >>>> temporally by re-adding the dependencies, something like this: >>>> >>>> Dependencies on .aar artifact: >>>> >>>> dependencies { >>>> compile fileTree(dir: 'libs', include: ['*.jar', '*.aar']) >>>> compile ('com.android.support:support-v4:19.0.1') >>>> compile ('no.sysco:syscoabslibrary:4.1.2') >>>> compile ('no.sysco:syscodrawerlibrary:1.2') >>>> } >>>> >>>> Dependencies on other library project: >>>> >>>> dependencies { >>>> compile fileTree(dir: 'libs', include: ['*.jar', '*.aar']) >>>> compile ('no.sysco:syscobasecontainer:1.3') >>>> compile ('no.sysco:syscotouchgallery:1.2') >>>> compile ('no.sysco:syscoabslibrary:4.1.2') // <- this one is a >>>> transitive dependencies and is duplicated. >>>> compile ('no.sysco:syscodrawerlibrary:1.2') // <- this one is a >>>> transitive dependencies and is duplicated. >>>> compile ('com.google.android.gms:play-services:4.2.42') >>>> } >>>> >>>> If I don't duplicate the dependencies, it won't compile. >>>> >>> -- >>> 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. >> > > > > -- > > Thank you, > Malachi de Ælfweald | Technology Team | Upsight > Mobile: +1 503-307-1597 > Skype: malachid69 | Find me on LinkedIn<http://www.linkedin.com/in/malachid/> > > Get the Best Mobile Marketing and Analytics free <http://www.upsight.com/>| > Upsight > is Hiring! <http://www.upsight.com/company/#careers> > > Check Out Our Blog <http://upsight.com/blog> | Follow Us > @GetUpsight<http://www.twitter.com/getupsight%20%20> > > -- > 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.
