simple library publishing with Gradle

So, you switched to Gradle and just finished you new shiny Android library (or java library). And of course you want to share it with the community.

Here’s a quick guide for those who never published their libraries before.

What is maven central?

In java world libraries are usually stored in a big repository called Maven Central. You may think of it as of the NPM repository for Node.js or as of PyPI for Python.

It lets you quickly find a library at It is also used by other tools like Gradle, Please. Finally, gradle uses this repo if you included mavenCentral() into your repositories section.


First, you will have to register. No, don’t try to find a ‘Register’ link on the Maven Central website. Instead, you should register on the Sonatype website.

What is Sonatype? They are the guys who created Maven back in 2002. But don’t try to find a registration link on their site either, instead go to their issue tracker. (well-known JIRA) and register there:

Next, create a new issue.

In the issue details fill in your library description and summary, specify project URL if any and version control URL (like bitbucket or github link). Ensure you have a valid group id. It’s should be somehow related to your package and should contain at least one dot in it. So, names like ‘johndoe’ are invalid, but ‘com.johndoe’ are ok if you own the ‘’ website. If you don’t own any website - you may use your version control hosting name, e.g. com.bitbucket.johndoe or com.github.johndoe.

Then - relax and wait. It may take up to 2 business days to process your ticket manually.

After that you will receive a confirmation that your configuration has been prepared and you can publish your library.

Gradle setup

There are many possible ways of how to set up your gradle for maven publishing. I used a file I found in some other repository and I like it’s separated from the main build.gradle.

Here it is:

 * Copyright 2013 Chris Banes
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * See the License for the specific language governing permissions and
 * limitations under the License.

apply plugin: 'maven'
apply plugin: 'signing'

def isReleaseBuild() {
        return VERSION_NAME.contains("SNAPSHOT") == false

def getReleaseRepositoryUrl() {
                        : ""

def getSnapshotRepositoryUrl() {
                        : ""

def getRepositoryUsername() {
        return hasProperty('NEXUS_USERNAME') ? NEXUS_USERNAME : ""

def getRepositoryPassword() {
        return hasProperty('NEXUS_PASSWORD') ? NEXUS_PASSWORD : ""

afterEvaluate { project ->
        uploadArchives {
                repositories {
                        mavenDeployer {
                                beforeDeployment { MavenDeployment deployment -> signing.signPom(deployment) }

                                pom.groupId = GROUP
                                pom.artifactId = POM_ARTIFACT_ID
                                pom.version = VERSION_NAME

                                repository(url: getReleaseRepositoryUrl()) {
                                        authentication(userName: getRepositoryUsername(), password: getRepositoryPassword())
                                snapshotRepository(url: getSnapshotRepositoryUrl()) {
                                        authentication(userName: getRepositoryUsername(), password: getRepositoryPassword())

                                pom.project {
                                        name POM_NAME
                                        packaging POM_PACKAGING
                                        description POM_DESCRIPTION
                                        url POM_URL

                                        scm {
                                                url POM_SCM_URL
                                                connection POM_SCM_CONNECTION
                                                developerConnection POM_SCM_DEV_CONNECTION

                                        licenses {
                                                license {
                                                        name POM_LICENCE_NAME
                                                        url POM_LICENCE_URL
                                                        distribution POM_LICENCE_DIST

                                        developers {
                                                developer {
                                                        id POM_DEVELOPER_ID
                                                        name POM_DEVELOPER_NAME

        signing {
                required { isReleaseBuild() && gradle.taskGraph.hasTask("uploadArchives") }
                sign configurations.archives

        //task androidJavadocs(type: Javadoc) {
                //source = android.sourceSets.main.allJava

        //task androidJavadocsJar(type: Jar, dependsOn: androidJavadocs) {
                //classifier = 'javadoc'
                //from androidJavadocs.destinationDir

        task androidSourcesJar(type: Jar) {
                classifier = 'sources'

        artifacts {
                archives androidSourcesJar

You may also download it from here.

Put this file next to your build.gradle and create a file in the same directory:






This should not be added to the version control as it contains some private information.

Finally, in your build.gradle just add this line somewhere at the end:

apply from: 'maven-push.gradle'

Now you’re almost ready to publish.

Ensure you have gpg set up

You should sign your package with GPG. If you never used it - first create the GPG keys:

$ gpg --gen-key

Next, find your key ID:

$ gpg --list-keys

There the first line will be like pub XXXXX/YYYYYYYY <date>. Remember that ‘YYYYYYYY’ part, it’s you key ID.

Now, publish your keys:

$ gpg --keyserver hkp:// --send-keys YYYYYYYY
$ gpg --keyserver hkp:// --send-keys YYYYYYYY

You may use other key servers as well. You may also want to ensure your keys were published:

$ gpg --keyserver hkp:// --search-keys # Use your email

Pushing the archives

Now you can do:

$ gradle uploadArchives

Your library will be built, signed and pushed to the sonatype repo. Please, ensure that ‘signing’ stage was not skipped. It is skipped if your library name is ending with “-SNAPSHOT”, but for releases signing is mandatory.

If all went fine - go to the OSSRH web UI and look for your ‘staging’ library. It should be somewhere at the end of the list. Select it, and press ‘Close’ button. Closing a library actually means that you’re ready to release it. Another option is ‘dropping’ a library, which means removing it from the list. If closing went fine - you should see a ‘Release’ button active. Press it and then get back to JIRA and post a comment there that you promoted you library.

After that you should get a response from Sonatype that your library will be available in ~10 minutes and it will be synced with the Maven Central in the next few hours.

To me that meant that I could use my library in other projects in a few minutes after I released it (e.g. using in gradle like ‘compile groupID:name:version’), but the found it only next morning.

So, that’s it, and if you still have any problems - ask Sonatype support, I found them to be very helpful. Happy coding!

I hope you’ve enjoyed this article. You can follow – and contribute to – on Github, Twitter or subscribe via rss.

Aug 10, 2014