Skip to end of metadata
Go to start of metadata

Atlassian provides various Maven repositories for Plugin Developers.We recommend using the Atlassian Plugin SDK to make sure you've got the correct settings to use our servers.

The Plugin SDK handles almost all of this Maven tweaking for you. The SDK includes an embedded Maven installation and correct settings.xml that will be kept up to date as necessary. We believe it makes the plugin development process much easier. For more information, see here.

Atlassian Maven Proxy 

The Atlassian Maven proxy sits in front of all of our other Maven repositories, as well as third-party repositories like iBiblio and Codehaus. This should provide all artifacts needed to build our products and plugins. In the basic case, this is the only repository you need to know about.

Atlassian Private Repository

The Atlassian private repository contains the source artifacts of our closed-source components. Atlassian staff has read and write access.

Atlassian 3rdParty Repository

The third-party directory contains jars that we are not allowed to redistribute, such as those from Sun. Atlassian staff has read and write access.

Atlassian Public Repository

The Atlassian public repository contains all artifacts necessary to build a plugin for our products. It contains binaries, source and javadoc of our opensource components, and binaries and javadoc for our closed-source components. Anyone can read from this repository. Only Atlassian staff can write to it.


  1. Hi,

     What is the difference/relationship between and

    My company proxies the first however the second appears to contain newer release artefacts that the latter does not (for example the latest version of oscore).

     Are both required? If so which should be given a higher priority/ranking?


    1. I believe the latter is the one you should use as your reference. That said, I'm not sure exactly what the latter URL actually includes, if it's just the 'public' repository or also the 'contrib' and/or 'contrib-snapshot' repositories. Atlassian?

    2. To reply to that the former URL is the actual public repository and the later is the public proxy URL that proxies the public repository as well as some other repositories as described above.

      Of course when browsing the second URL you might not see some artifacts. This is when those have not already been queried.

  2. Anonymous

    It would be nice to provide self contained and clear documentation and not something halfway that always leave people having to do a lot of guesswork e.g. how about adding a simple settings.xml snippet with the correct repository configuration that includes 

    1. My apologies for your frustration. I've included a snippet for the repo; this same snippet exists in our SDK settings.xml. 

  3. Anonymous

    where could I check which dependencies are already included in plugin?

    for example for StashPlugin, created by at atlas-create-stash-plugin, the stash-rest dependency is already included.

    Also build-integration alreadyincluded. I  wanna look through the list of all default dependencies. Does it possible.

    At datail I am interested in stash-scm-git-api and stash-scm-git - should I add it manually in my pom.xml or not?

  4. If you are creating your plugin with atlas-create-stash-plugin, the generated pom.xml includes some dependencies on the Stash APIs.  If you want additional artifacts, refer to this page:

  5. Could it be possible to include javadocs and (when available) source artifacts in the public repositories?

    I mean, I use Netbeans and it is frustrating not having javadoc in the code completion and have to copy the class name and browse the on-line documentation. Maven allows to add javadoc and sources along with libraries and to download them to my local repository. So I can download javadoc (and sources when available) along with my dependencies.