With the launch of plugins.atlassian.com, the Confluence Plugin Repository SVN metadata has been deactivated. For existing clients, requests to confluence.atlassian.com for repository metadata are now transparently redirected to plugins.atlassian.com, which provides up-to-date plugin information in the same XML format as that served from the old repository proxy.

While Confluence installations with access to confluence.atlassian.com see no impact from this change, those installations which cannot access confluence.atlassian.com need special instructions.

Download the latest plugins.atlassian.com XML for your version of Confluence

PAC makes the plugin repository client data available at the URL

https://plugins.atlassian.com/server/legacy/confluence/xml/<bn>

where <bn> is the build number of the Confluence installation. The build number is visible at Admin -> System Information (near the bottom of the page). Build numbers for all released Confluence builds are also available here​.

Save the resulting file and place it on a Web server accessible from Confluence. This can be the same server as Confluence itself; for example, if you're running the standalone version of Confluence at http://localhost:8090, place the saved XML in the confluence directory inside your standalone installation.

Keeping the XML up to date

When a change is made on plugins.atlassian.com to a plugin's data, the generated XML will update at most one day after the change is made. Consider writing a cron job or similar to fetch the XML on a weekly basis and store it in your chosen location to ensure you are always up to date on plugin information.

Configure the Plugin Repository Client

Now go to Admin -> Plugins -> Confluence Atlassian Plugin Repository and click on the Configure link.

There are four plugin repository data source options:

  1. HTTP Data Source Generator - Plain text XML file served over HTTP. Never used, except for debugging.
  2. Subversion Generator (Deprecated) - Check out the metadata from SVN and generate the XML internally. As this uses the deprecated SVN metadata, it can be ignored.
  3. Local Generator (Deprecated) - Read the metadata off your local filesystem and generate the XML internally. As this uses the deprecated SVN metadata, it can be ignored.
  4. Proxy Client - pull XML data from another Confluence Plugin Repository Client that has been configured to act as a server.

In this case you would need to choose the Proxy Client option, as it is able to fetch XML from any server, not just plugins.atlassian.com.

Paste the URL to the XML data in the Data Source field and uncheck the Data Source Proxying option if it is checked. Then click Save and select Admin -> Plugin Repository, and the client should load the repository info as before.

RELATED TOPICS

Confluence Repository Client

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