Android Libraries: maven vs maven-publish gradle project-ThrowExceptions

Exception or error:

I’m building a large multi-module Android library, and need to publish the library to an internal company Artifactory.

Should I use the old maven plugin, or the new maven-publish plugin?

Note: The above two official plugins don’t fully support Android, so there are two community ports.

Also interesting – the Android Tools team deprecated the experimental gradle plugin that was based around the SoftwareComponent model – which is what the maven-publish plugin uses. Is maven-publish deprecated too then?

How to solve:

I would recommend you to use new maven publish plugin. Gradle deprecated the old maven plugin with Gradle 1.3. According to this Gradle blog post only parts of the SoftwareComponent model will be marked as deprecated and the rest is going to be ported:

… You may therefore be wondering what is happening to the Software Model. We’re in the process of porting the configuration DSL of the native support to the current model. So the declarative nature and strong modelling language will be the same. The rule engine that was part of the Software Model will be deprecated. Everything under the model block will be ported as extensions to the current model …

If you want an example for the maven-publish, Realm-Java uses it: https://github.com/realm/realm-java/blob/master/realm/realm-library/build.gradle

Leave a Reply

Your email address will not be published. Required fields are marked *