maven integration with third party libs built by gradle

[mores]

I have been a maven fan for quite some time, and I would like to continue to use maven but I am starting to run into issues.

I am using maven-android-sdk-deployer to deploy google artifacts.
I am using android-maven-plugin to build.

I am now trying to use a 3rd party lib: https://github.com/DenisMondon/material-design-library
Published here: http://jcenter.bintray.com/com/blunderer/materialdesignlibrary/2.0.4/

I added jcenter as a repo, added the dependency:

<dependency>
                <groupId>com.blunderer</groupId>
                <artifactId>materialdesignlibrary</artifactId>
                <version>2.0.4</version>
                <type>aar</type>
</dependency>

But it looks like his pom is referencing jars not aars. So maven is complaining about missing dependencies.

Is there an easy fix for this or will this force me to move to gradle ?

-Thanks

[Manfred Moser]

If the pom produced by Gradle is invalid you should report the issue to the project owner and maybe to the SDK team.

As a workaround you could craft your own pom and upload the aar with a corrected pom to your own repository manager.

Manfred

> --
> You received this message because you are subscribed to the Google Groups "Maven Android Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to maven-android-deve...@googlegroups.com <mailto:maven-android-deve...@googlegroups.com> .
> For more options, visit https://groups.google.com/d/optout <https://groups.google.com/d/optout> .

[William Ferguson]

My recollection is that this was a problem with early versions of Gradle.

But I seem to recall it being fixed about 12 months ago.

So you could try rebuilding the 3rd party project with a recent version of Gradle and using that artefact.

William

On Wednesday, January 20, 2016 at 4:44:16 AM UTC+10, Manfred Moser (simpligility) wrote:

If the pom produced by Gradle is invalid you should report the issue to the project owner and maybe to the SDK team.

As a workaround you could craft your own pom and upload the aar with a corrected pom to your own repository manager.

Manfred

mores wrote on 19.01.2016 08:43:

> I have been a maven fan for quite some time, and I would like to continue to use maven but I am starting to run into issues.
>
> I am using maven-android-sdk-deployer to deploy google artifacts.
> I am using android-maven-plugin to build.
>
> I am now trying to use a 3rd party lib: https://github.com/DenisMondon/material-design-library
> Published here: http://jcenter.bintray.com/com/blunderer/materialdesignlibrary/2.0.4/
>
> I added jcenter as a repo, added the dependency:
>
> <dependency>
>                 <groupId>com.blunderer</groupId>
>                 <artifactId>materialdesignlibrary</artifactId>
>                 <version>2.0.4</version>
>                 <type>aar</type>
> </dependency>
>
> But it looks like his pom is referencing jars not aars. So maven is complaining about missing dependencies.
>
> Is there an easy fix for this or will this force me to move to gradle ?
>
> -Thanks
>
> --
> You received this message because you are subscribed to the Google Groups "Maven Android Developers" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to maven-android-developers+unsub...@googlegroups.com <mailto:maven-android-developers+unsubscribe@googlegroups.com> .