strange issue with aar and class resolution

Alex O'Ree

unread,

Oct 6, 2015, 4:14:07 PM10/6/15

to maven-androi...@googlegroups.com

I've noted the following behavior and was wondering if anyone has ran
into this or had a solution.

Case 1:
Gradle produced AAR, published to nexus
Maven imported AAR, can't find classes defined in the AAR.

workaround: none that I know. Gradle doesn't publish the class jar
from the aar project to nexus.

Also a related scenario

Case 2:
Maven produced AAR published to nexus
Gradle imports AAR, but won't resolve dependencies defined in the pom

workaround: manually at the AAR's dependencies into the gradle project

Alex O'Ree

unread,

Oct 9, 2015, 7:05:49 AM10/9/15

to maven-androi...@googlegroups.com

ping, anyone receiving this?

William Ferguson

unread,

Oct 14, 2015, 5:05:32 AM10/14/15

to Maven Android Developers

case 1 is the class jar contained within the aar?

case 2 - ditch Gradle or get the Gradle team to pull up their socks.

William

Crossmo

unread,

Oct 29, 2015, 2:43:04 PM10/29/15

to Maven Android Developers

This may be related to an AAR not well packaged, as reported as https://github.com/simpligility/android-maven-plugin/issues/692

Crossmo

unread,

Oct 29, 2015, 2:43:04 PM10/29/15

to Maven Android Developers

On Wednesday, October 14, 2015 at 5:05:32 PM UTC+8, William Ferguson wrote:

case 1 is the class jar contained within the aar?

I don't think so. Maybe his AAR could be packaged with a previous version of andoid-maven-plugin, like the one I used in my case. https://github.com/simpligility/android-maven-plugin/issues/692

Reply all

Reply to author

Forward