Atlassian provides various Maven repositories for Plugin Developers. You can use the Example settings.xml we provide to configure your development environment to use these repositories.
 | We've released a new Plugin SDK which 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.
If you find an artifact that is required, but not available through the Maven Proxy, please create an issue in the Developer Network CPDK JIRA project
Legacy Maven 1 Repository
The Legacy Maven repository contains older components that are necessary for compatibility with previous releases of our products. This is a read-only repository. Any new artifacts should be deployed to one of the Maven 2 repositories below.
Atlassian Private Repository
The Atlassian private repository contains the source artifacts of our closed-source components. 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.
- http://maven.atlassian.com/private
- http://maven.atlassian.com/private-snapshot
- http://maven.atlassian.com/3rdparty
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.
Atlassian Contrib Repository
The Atlassian contrib repository is a resource that we make available for our third-party developers. You can use this to deploy and release your plugins as well as the shared libraries that many developers have created. Anyone can read from this repository. Atlassian staff and Developer Network Committers have write access using your Developer Network credentials.
Those wishing to deploy their plugins and libraries to this repository need to add the following to their pom.xml:
<distributionManagement>
<repository>
<id>atlassian-contrib</id>
<name>Atlassian Contrib Repository</name>
<url>dav:https://maven.atlassian.com/contrib</url>
</repository>
<snapshotRepository>
<id>atlassian-contrib-snapshot</id>
<name>Atlassian Contrib Snapshot Repository</name>
<url>dav:https://maven.atlassian.com/contrib-snapshot</url>
</snapshotRepository>
</distributionManagement>
Comments (3)
Jul 21, 2008
Alan Mosely says:
Hi, What is the difference/relationship between https://maven.atlassian.c...Hi,
What is the difference/relationship between https://maven.atlassian.com/public and https://maven.atlassian.com/repository/public?
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?
Thanks,
Jul 21, 2008
David Peterson [CustomWare] says:
I believe the latter is the one you should use as your reference. That said, I'm...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?
Jul 22, 2008
Samuel Le Berrigaud says:
To reply to that the former URL is the actual public repository and the later is...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.