Atlassian Maven Repositories

Links
Developer Network

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.

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 be the only Maven 2 repository you need in your settings.xml file (or configured in your own proxy).

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.

If you are developing Jira plugin you will need to add this repository to your settings.xml. Have a look at the Example settings.xml for how to declare such a repository in your settings.xml.

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.

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>

Also ensure you have configured your settings.xml correctly so that you will be authenticated.

Labels

proxy proxy Delete
repositories repositories Delete
repository repository Delete
maven maven Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (29)

 

  1. Jun 03, 2008

    David Peterson [CustomWare] says:

    Hi guys, Visiting https://maven.atlassian.com/repository/public currently reque...

    Hi guys,

    Visiting https://maven.atlassian.com/repository/public currently requests a username and password to proceed anywhere. I'm sure this was not previously the case, and I'm guessing it is not intentional, since it blocks downloading from the repo unless you have a developer user id - and I'm not even certain that will work either. Can this be fixed please? It's making it very difficult to build projects.

    1. Jun 04, 2008

      Tim Moore says:

      David, Please try this again. I believe we have it fixed now.

      David,

      Please try this again. I believe we have it fixed now.

      1. Nov 02, 2008

        Andrey Mikulov says:

        It's again asks authentication. Also interesting - who can access https://mave...

        It's again asks authentication.

        Also interesting - who can access https://maven.atlassian.com/repository/internal ? When I try to build package whith plugin, maven want to download many pom-files, that is not found on public, but exists in internal (find by google...)...

        1. Nov 02, 2008

          James Dumay says:

          Hey Andrey, Which plugin is trying to download from https://maven.atlassian.com...

          Hey Andrey,

          Which plugin is trying to download from https://maven.atlassian.com/repository/internal ? This shouldn't be happening at all.

          https://maven.atlassian.com/repository/internal is an Atlassian staff only repository that contains artifacts we cannot distribute for legal purposes and artifacts for internal tools we do not wish the world to have access to.

          Thanks,

          James

          1. Nov 03, 2008

            Andrey Mikulov says:

            I make empty JIRA plugin project and try to package them in Eclipse with maven 2...

            I make empty JIRA plugin project and try to package them in Eclipse with maven 2.0.9, maven but always can't find this files:

            osworkflow-2.8.0.pom
            webwork-17Jan08-jiratld.pom
            ofbcore-share-2.1.1-atlassian-2008-04-23.pom
            ofbcore-entity-2.1.1-atlassian-2008-04-23.pom
            javacvs-2007-04-04-patched.pom
            atlassian-trackback-0.11.pom
            jfreechart-1.0.4.pom
            urlrewrite-2.5.2.pom
            wstx-asl-3.2.4.pom
            httpunit-1.5.4-patched-2007-08-09.pom
            cargo-core-uberjar-1.0-atlassianpatch-CARGO-553.pom
            concurrent-1.3.4-withdebug.pom

            I find some of them by google in internal Atlassian repository (i.e. - webwork-17Jan08-jiratld.pom)... I can build and package project without this files, but building of plugin is more slowly when maven always try to find this files in many internet repositories through slow proxy... Is it possible to remove dependencies on this files or add it to public repository for normal maven caching?

  2. 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,

    1. 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?

    2. 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.

  3. Jul 21, 2008

    Ed Seymour says:

    We're also noticing inconsistencies, or at the least duplications, with group id...

    We're also noticing inconsistencies, or at the least duplications, with group ids. For example the oscore artefact appears under /opensymphony/oscore in addition to just simply /oscore.

    https://maven.atlassian.com/repository/public/oscore/oscore/ https://maven.atlassian.com/repository/public/opensymphony/oscore/

    1. Jul 22, 2008

      Samuel Le Berrigaud says:

      Hi Ed, unfortunately, this is not only up to us. Sometimes the project choose t...

      Hi Ed,

      unfortunately, this is not only up to us. Sometimes the project choose to change their groupId to better match maven conventions on that topic.

      The opensymphony project have suffered from that and can be rather inconsistent at times.

  4. Jul 21, 2008

    John Allen says:

    let's take a look at part of my poor proximity properties file, maybe someone in...

    let's take a look at part of my poor proximity properties file, maybe someone in Atlassian can explain what all these repos are for and which ones i really need!

    atlassian.public.release.m2.RemotePeer.remoteUrl=https://maven.atlassian.com/public/
    atlassian.public.snapshot.m2.RemotePeer.remoteUrl=https://maven.atlassian.com/public-snapshot/

    atlassian.public.release.m1.RemotePeer.remoteUrl=https://maven.atlassian.com/maven1/

    # Sigh, Atlassian has a mix of m1 and m2 layouts under one repo URL.
    atlassian.alt-public.release.m1.RemotePeer.remoteUrl=https://repository.atlassian.com/
    atlassian.alt-public.release.m2.RemotePeer.remoteUrl=https://repository.atlassian.com/

    atlassian.contrib.release.m2.RemotePeer.remoteUrl=https://maven.atlassian.com/contrib/

    And by the looks of it i also need to add:

    https://maven.atlassian.com/repository/public/

    I'm sure there's some wisdom to all this and that supporting legacy POMs may play a part, it's just that right now I can't work out what I really do and what I really don't need.

    Thanks,
    John

    1. Jul 21, 2008

      Samuel Le Berrigaud says:

      Hi John, all you should need is to define this repository: https://maven.atlass...

      Hi John,

      all you should need is to define this repository: https://maven.atlassian.com/repository/public

      This is our public proxy that actually proxies all of our different repositories. This should simplify your configuration

      SaM

      1. Jul 22, 2008

        Ed Seymour says:

        Thanks for the clarification - we've been scratching our head over this. Err, j...

        Thanks for the clarification - we've been scratching our head over this.

        Err, just a thought, but if this is your one repository to rule them all, then wouldn't it be a good idea to say as much above? You do realise that you direct us to various other repositories, but nowhere is this mentioned other than in our comments! 

        1. Jul 22, 2008

          Samuel Le Berrigaud says:

          Good point Ed. Thanks for pointing that out. I have updated the page and hopeful...

          Good point Ed. Thanks for pointing that out. I have updated the page and hopefully it is more clear now.

          1. Jul 22, 2008

            Ed Seymour says:

            Smashing - thanks guys

            Smashing - thanks guys

          2. Jul 22, 2008

            Alan Mosely says:

            Sorry just to be perfectly clear, looking at the snippet of the proximity config...

            Sorry just to be perfectly clear, looking at the snippet of the proximity config file John posted, all he would need to state to achieve what he is currently having to do with 5 different repos would be:

             

            atlassian.public.release.m2.RemotePeer.remoteUrl=https://maven.atlassian.com/repository/public

            atlassian.public.snapshot.m2.RemotePeer.remoteUrl=https://maven.atlassian.com/repository/public

            atlassian.public.release.m1.RemotePeer.remoteUrl=https://maven.atlassian.com/repository/public

            atlassian.public.snapshot.m1.RemotePeer.remoteUrl=https://maven.atlassian.com/repository/public

             

            Is that correct?

            Thanks,

            1. Jul 22, 2008

              Samuel Le Berrigaud says:

              Hi Alan, that looks alright. I don't believe you guys need our SNAPSHOTs, do ...

              Hi Alan,

              that looks alright.

              I don't believe you guys need our SNAPSHOTs, do you? I wouldn't depend on any f the SNAPSHOTs we produce. We just use them internally, and even then try to minimise our usage f them

  5. Jul 28, 2008

    Alan Mosely says:

    Hi, Thanks for the help, we are now proxying your 'master' repository but have ...

    Hi,

    Thanks for the help, we are now proxying your 'master' repository but have ran into an issue with one of your artifacts.

    We have found that the org.eclipse.equinox:common:3.3.0 artifact (https://maven.atlassian.com/repository/public/org/eclipse/equinox/common/3.3.0/) has a pom but not a corresponding jar (the jar is not correctly named).

    This is an issue for us as one of our (external) dependencies specifies this artifact as it's dependency with a version range, so although we normally resolve the latest valid version (3.3.0-v20070426) of this artifact from http://repo1.maven.org/maven2, Maven considers 3.3.0 to be the 'latest' and attempts to resolve it from the Atlassian repo instead of 'central' leading to build failures.

    Could you please remove this invalid pom or rename the corresponding artifact?

    PS: We wanted to raise this via a support request but there is no corresponding JIRA project, what is the correct channel for these requests?

    Many thanks,

    1. Jul 28, 2008

      Samuel Le Berrigaud says:

      Hi Alan, I am going to look into this. Thanks for pointing that out. I don't b...

      Hi Alan,

      I am going to look into this. Thanks for pointing that out. I don't believe we have a place to raise issues against our repository. This is probably a good idea and I will discuss it internally.

      Regards.

      1. Aug 08, 2008

        Ed Seymour says:

        We've hit similar problems attempting to build a jira plugin. We're finding depe...

        We've hit similar problems attempting to build a jira plugin. We're finding dependencies to artefact versions where there appears to be corruption in the repository, e.g. empty version folder of missing jars.

        I raised an issue (CPDK-28) on Wednesday, but so far no response

        The following URLs link to _empty_ or have _missing jars_ for required artefacts in the repository, all of which are a dependeny of jira-3.12.2

        https://maven.atlassian.com/repository/public/net/java/dev/urlrewrite/urlrewrite/2.5.2/
        https://maven.atlassian.com/repository/public/atlassian-mail/atlassian-mail/1.5/
        https://maven.atlassian.com/repository/public/ofbcore/ofbcore-entity/2.1.1-atlassian-2007-05-07/
        https://maven.atlassian.com/repository/public/osworkflow/osworkflow/2.8.0/
        https://maven.atlassian.com/repository/public/webwork/webwork/30Apr07-jiratld/
        https://maven.atlassian.com/repository/public/jcaptcha/jcaptcha/all-1.0-RC2.0.1-atlassian-2007-03-07/
        https://maven.atlassian.com/repository/public/javacvs/javacvs/2007-04-04-patched/
        https://maven.atlassian.com/repository/public/jfreechart/jfreechart/1.0.4/

        In addition no maven2 artefact found for atlassian-gzipfilter:atlassian-gzipfilter:jar:1.2 but this is available under the more modern maven2 style group name (com.atlassian.gzipfilter) here: https://maven.atlassian.com/repository/public/com/atlassian/gzipfilter/atlassian-gzipfilter/1.2/ either the dependencies in the atlassian-jira pom need to be updated or the artefact needs to be duplicated under the old-style group name.

        1. Aug 15, 2008

          Tim Moore says:

          Ed, Sorry for the delay in our response. We're looking into this now.

          Ed,

          Sorry for the delay in our response. We're looking into this now.

        2. Aug 17, 2008

          Samuel Le Berrigaud says:

          Hi Ed, Jira is still using maven1 and therefore some of their dependencies are ...

          Hi Ed,

          Jira is still using maven1 and therefore some of their dependencies are not available in the maven2 repository. We are slowly going towards a point where they all are in a maven2 repository though.

          So for now, for resolving Jira dependencies, you still have to declare the maven1 repository in your settings.xml. The example settings.xml has such an entry you can copy in your own setting.xml.

  6. Sep 01, 2008

    Hamish Willee says:

    Hi I'm building the default example confluence archetype, using the default exam...

    Hi
    I'm building the default example confluence archetype, using the default example settings links from this page. However I'm getting two missing file messages. I fixed one by manually downloading the dependency. The other shown below. Any ideas what I might have done wrong to set this up?

    I am using Maven version: 2.0.9, Java version: 1.4.2_18, OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

    Note that this version of Maven stores its settings in a \conf directory.

    Error

    1) com.atlassian.confluence:confluence-webapp:war:2.61

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=com.atlassian.confluence -DartifactId=confluence-webapp -Dversion=2.61 -Dpackaging=war -Dfile=/path/to/file

    Alternatively, if you host your own repository you can deploy the file there:
    mvn deploy:deploy-file -DgroupId=com.atlassian.confluence -DartifactId=confluence-webapp -Dversion=2.61 -Dpackaging=war -Dfile=/path/to/file -Durl=[url]
    -DrepositoryId=[id]

    Path to dependency:
    1) com.symbian.confluence.plugins:contenttypeuid:atlassian-plugin:2.6.1
    2) com.atlassian.confluence:confluence-webapp:war:2.61

    1. Sep 01, 2008

      James Dumay says:

      Hey Hamish, The problem is that the dependency version for Confluence has been ...

      Hey Hamish,

      The problem is that the dependency version for Confluence has been mistyped - it should be 2.6.1 instead of 2.61 (missing a perioid). You can find the confluence version as a property inside the POM file you have created.

      Thanks

      James

      Build dude @ Atlassian 

  7. Sep 01, 2008

    Hamish Willee says:

    Also, after adding the two dependencies (webapp, confluence.jar) the mvn -compil...

    Also, after adding the two dependencies (webapp, confluence.jar) the mvn -compile builds without error and I can see the .class file.
    However in eclipse I have the following error
    "The project was not built since its build path is incomplete. Cannot find the class file for com.atlassian.user.User. Fix the build path then try building this project contenttypeuid Unknown Java Problem"
    Looking at my imports, this isn't in my classpath - where is it?
    import com.atlassian.user.User;

    I have already added M2_REPO to my classpath (C:/Documents and Settings/hamishw/.m2/repository/)

    Regards
    Hamish

    1. Sep 01, 2008

      James Dumay says:

      Hey Hamish, You might want to try q4e which is an eclipse plugin that can read ...

      Hey Hamish,

      You might want to try q4e which is an eclipse plugin that can read maven POM files and produce eclipse projects for you. Adding the entire local maven repository to your classpath will cause all sorts of issues as multiple versions of the same jar can exist in this location.

      Thanks

      James

      1. Sep 01, 2008

        Hamish Willee says:

        Hi James Thanks very much. Proper release number fixed both problems - and I wil...

        Hi James
        Thanks very much. Proper release number fixed both problems - and I will try the plugin.
        Now to the real bit of the work!
        Regards
        Hamish

        1. Sep 01, 2008

          James Dumay says:

          Any time

          Any time

  8. Nov 18, 2008

    David Fischer says:

    Hi, I'm building a JIRA plugin using the standard archetype, and everything wor...

    Hi,

    I'm building a JIRA plugin using the standard archetype, and everything works fine except that I couldn't figure out how to automatically publish my JAR artefact to the Atlassian contrib repository? I did configure the repository in my pom.xml file and my login/password in settings.xml, as well as the SCM repository, and I tried using the release:perform objective, but it fails with the following error: [ERROR] No SCM URL was provided to perform the release from

    Is there any documentation on how to automate the releasing of a plugin, besides http://confluence.atlassian.com/display/DEVNET/Releasing+your+plugin (step 5)?

    Thanks,

    David.


Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.