On 10 Apr 2014, at 8:19 am, Xavier Ducrohet <[email protected]> wrote:
> it's an aar file. It seems to happen only when the dependencies is coming > from a maven repositories (vs another sub-project). > > The pom contains <packaging>aar</packaging> > > Any other details I can provide? What’s the dependency declaration look like? eg is it in a build.gradle or a pom? > > > On Wed, Apr 9, 2014 at 2:55 PM, Adam Murdoch <[email protected]> > wrote: > > > On 10 Apr 2014, at 1:19 am, Xavier Ducrohet <[email protected]> wrote: > >> When building a project that depends on an aar artifact I see the warning: >> >> Relying on packaging to define the extension of the main artifact has been >> deprecated and is scheduled to be removed in Gradle 2.0 >> >> I'd like to fix this ASAP since 2.0 will be coming soon, but I'm not sure >> how to do this. >> >> At first I thought it was due to querying ResolvedArtifact.getType() in my >> code but that doesn't seem to be it. >> >> The message seems to come from >> GradlePomModuleDescriptorBuilder.addMainArtifact, where it outputs the >> message whenever your artifact packaging value is different from pom and jar. >> >> Is there something I can/need to fix in preparation for 2.0? If so, how? > > Possibly. What does the dependency look like? > > > -- > Adam Murdoch > Gradle Co-founder > http://www.gradle.org > VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting > http://www.gradleware.com > > Join us for Gradle Summit 2014, June 12th and 13th in Santa Clara, CA: > http://www.gradlesummit.com > > -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com Join us for Gradle Summit 2014, June 12th and 13th in Santa Clara, CA: http://www.gradlesummit.com
