Bad maven scope declaration for AAR dependency

[Tomáš Procházka]

I have one gradle related question.

This project 

https://github.com/ManuelPeinado/FadingActionBar

has one aar module  that depend on another one and on app compat library.

But during deploying to the maven repository, gradle don't generate <scope>aar</scope> to the dependency declaration.

So by maven definition it mean that dependency should be .jar not .aar.

It is bug of gradle itself or bug in your android plugin which define aar?

Problem is described also here:

https://github.com/ManuelPeinado/FadingActionBar/issues/70

[Tomáš Procházka]

Sorry. I don't mean <scope> but <type>

Dne úterý, 5. srpna 2014 22:23:36 UTC+2 Tomáš Procházka napsal(a):

[Jake Wharton]

Type isn't needed. The pom for ABC is queried and the declared packaging (aar) will be used.

--
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 adt-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tomáš Procházka]

Are you sure? Because when I use it in the maven base project I get

[ERROR] Failed to execute goal on project app-telekomTv: Could not resolve dependencies for project ...:apk:1.0.2-SNAPSHOT: The following artifacts could not be resolved: com.

github.manuelpeinado.fadingactionbar:fadingactionbar:jar:3.1.2, com.android.support:appcompat-v7:jar:21.0.0-rc1: Failure to find com.github.manuelpeinado.fadingactionbar:fadingactionbar:jar:3.1.2 in h

ttps://... was cached in the local repository, resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced -> [Help 1]

Dne úterý, 5. srpna 2014 22:33:42 UTC+2 Jake Wharton napsal(a):

[Vyacheslav Blinov]

You are referring to Gradle behaviour here. But according to maven rules you should have type in your dependency declaration in pom (and pom is maven specific file). Maybe there are more build/dependency management systems that rely on type of dependency, but afaik at least maven users are, unfortunately, in trouble here and have to use exclusions hack.
I would say it is a bug in pom generation since pom-specific rules werent preserved.

06 авг. 2014 г. 0:33 пользователь "Jake Wharton" <jakew...@gmail.com> написал:

[William Ferguson]

This is bad. Similar to Gradle versions of "+" being copied into Maven poms.

If it is a Gradle Android plugin doing this then the plugin needs to be fixed.

Maven repos like Central should reject artifacts that provide malformed poms. To date they have relied upon everyone being good citizens but it seems like stricted enforcement is now required.

William

[Tomáš Procházka]

2014-08-07 13:20 GMT+02:00 William Ferguson <william....@xandar.com.au>:

This is bad. Similar to Gradle versions of "+" being copied into Maven poms.

If it is a Gradle Android plugin doing this then the plugin needs to be fixed.

 So you think that this is issue of Gradle Android plugin not gradle itself?

 

Maven repos like Central should reject artifacts that provide malformed poms. To date they have relied upon everyone being good citizens but it seems like stricted enforcement is now required.

I completely agree!

 

[Jake Wharton]

On Thu, Aug 7, 2014 at 5:23 AM, Tomáš Procházka <tomas.p...@atomsoft.cz> wrote:

2014-08-07 13:20 GMT+02:00 William Ferguson <william....@xandar.com.au>:

This is bad. Similar to Gradle versions of "+" being copied into Maven poms.

If it is a Gradle Android plugin doing this then the plugin needs to be fixed.

 So you think that this is issue of Gradle Android plugin not gradle itself?

It isn't. I can do this in any Gradle project, Android or not. This is user education issue that is not at all specific to Android.

 

[Xavier Ducrohet]

Someone reported this to me a few weeks ago already, but I didn't have time to look into it.

I just email the Gradle dev list asking for their opinion on this, since it's Gradle itself that's generating the POM (our plugin doesn't do anything).

--

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 adt-dev+u...@googlegroups.com.
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!

[William Ferguson]

Great, thanks for the follow up Xavier.

--
You received this message because you are subscribed to a topic in the Google Groups "adt-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/adt-dev/PM50ZXFXN_k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to adt-dev+u...@googlegroups.com.

[Xavier Ducrohet]

BTW, here the bug that was filed a while ago for this: https://code.google.com/p/android/issues/detail?id=72807

I'll update the bug when I have more information.

[William Ferguson]

It doesn't sound like a user education issue. 

It sounds like the Gradle Maven plugin that is generating the Maven pom is not doing what it should. Any idea where I can report an issue for it?

--
You received this message because you are subscribed to a topic in the Google Groups "adt-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/adt-dev/PM50ZXFXN_k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to adt-dev+u...@googlegroups.com.

[Tomáš Procházka]

Thanks. I also think that it will be bug in Gradle itself, but android plugin should be responsive for define "aar" type itself and Gradle should ask for it during deploy.

--
Ing. Tomáš Procházka

--
You received this message because you are subscribed to a topic in the Google Groups "adt-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/adt-dev/PM50ZXFXN_k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to adt-dev+u...@googlegroups.com.

[Tomáš Procházka]

It looks that nobody reply on it :-(

http://gradle.1045684.n5.nabble.com/Publishing-a-maven-artifact-depending-on-an-aar-or-other-non-quot-jar-quot-artifacts-td5713019.html

Gradle doesn't have some issue tracking tool?

Dne čtvrtek, 7. srpna 2014 21:15:01 UTC+2 Xavier Ducrohet napsal(a):

[Luke Daley]

On 6 September 2014 at 3:21:21 am, Tomáš Procházka (tomas.p...@gmail.com) wrote:

It looks that nobody reply on it :-(

http://gradle.1045684.n5.nabble.com/Publishing-a-maven-artifact-depending-on-an-aar-or-other-non-quot-jar-quot-artifacts-td5713019.html

Gradle doesn't have some issue tracking tool?

https://issues.gradle.org.

[Tomáš Procházka]

Any progress in this issue?

Here was suggested #6 solution for this problem with current version of the Gradle, so it is not neccesary to wait for Gradle team which ignore all bug reports :-(

Dne pátek, 8. srpna 2014 1:24:22 UTC+2 Xavier Ducrohet napsal(a):

[David Carver]

Actually this is Gradle violating Maven standards.  The packaging type in maven only applies to that artifact, not any dependencies.  If a type is not specified on a dependency in a pom, maven assumes that it is JAR.   Gradle is breaking compatibility with other tooling in this particular case.

More info here:

http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html

Particularly in the examples.  If type is not specified, maven assumes jar.