Skip to main content
Jump to: navigation, search


Revision as of 09:16, 21 May 2013 by (Talk | contribs) (Deploying artifacts to

Eclipse Nexus Instance

The Eclipse Nexus instance is hosted at:

This repository allows Eclipse projects to publish their build artifacts into a centralized repository hosted by EMO.


  • Snapshots older than 30-days are automatically removed on a weekly basis

Getting a Nexus repo for your Project

Simply file a Bug and specify what project you'd like a Nexus repo for.

Pulling artifacts from Nexus

To use to pull artifacts for your project there are a few URLs that can be used.

Releases Group

This URL is a top-level aggregate of all project releases repositories. This URL is recommended if you just want to pull in releases from any project hosting artifacts on

Snapshots Group

This URL is a top-level aggregate of all project snapshots repositories. This URL is useful for developers who want to pull in artifacts that may have not yet been released usually nightlies.

Project Specific Repos

Finally you can also use a project specific repo if you only want to ensure you are only pulling artifacts from specific projects. To get the URLs for these projects you can navigate to and browse for the URL link for the specific project.

Deploying artifacts to

To deploy artifacts to you will need to use Hudson ( to configure a job for deploying your artifacts.

It is recommended that you use JDK 7 or higher as we have seen SSL Handshake issues when using JDK 6.

Initial Maven POM setup

Before Hudson can deploy your project's artifacts to Nexus you will need to do some setup on the Maven side to add a "distributionManagement" section to your project pom. An example below:

      <name>Project Repository - Releases</name>
      <name>Project Repository - Snapshots</name>

Replace instances of the word "project" with your project's name.

Note: It is important to ensure your ID's are "" as the Hudson instance is configured to use these IDs.

If you want to keep several snapshot versions use:


Hudson Job Setup

Using you will need to configure Maven to run the "deploy" goal.

There are 2 ways you might want to do this:

  1. Simply add the "deploy" goal as one of your Maven goals as part of your build
  2. Create separate jobs, one for building and one for deploying (if you want more control over when to deploy)

If you decided to go with creating separate jobs, your deploy job will need access to your build job's workspace, an easy way of making this work is to configure the build job, and the deploy job with the optional Use custom workspace configuration under Advanced project options.


Custom workspace.jpg

Replace <your build job project name> with the name of your project job, for example if your build job was named cbi-maven-plugins-build then your Directory should be /opt/public/jobs/cbi-maven-plugins-build/workspace. This setting should be configured in both your Build job and Deploy jobs.

Finally your deploy job should invoke an instance of Maven 3 with the "deploy" goal. The only additional option you need to ensure that's configured is to click Advanced and configure the Settings option and set it to Deploy to This custom settings file contains the necessary credentials in order for you to deploy to

Deploy settings.jpg

Deploying a jar to

It is possible to use the Maven deploy:deploy-file goal to push a jar file into via For every jar you wish to push into an associating pom.xml file is necessary.

The simplest pom.xml can be as follows:

<project xmlns="" xmlns:xsi="" xsi:schemaLocation="">
</project> has access to the same /shared as so placing your files somewhere there will allow hudson to be able to find it.

Configuring Hudson for mvn deploy:deploy-file

There are 3 settings which need to be configured:

  1. Goals: deploy:deploy-file
  2. Properties:
    url=<Your project's repo URL to push jar into>
  3. POM File: /path/to/pom.xml

For example: Mvn-deploy-file.png

Note: You will also need to configure your settings file to use Deploy to per instructions in the previous section for deploying artifacts.

Back to the top