Skip to main content
Jump to: navigation, search


This page provides information how to publish a Java project to the Nexus repository instance running at Readers are expected to be familiar with Maven concepts and Maven repository publishing. If this is not the case, we strongly suggest readers to first read the basics from Sonatype's documentation and the Apache Maven Deploy plugin.

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 7-days are automatically removed on a weekly basis with the minimum of 1 snapshot being retained.
  • All snapshots for a given GAV are automatically removed 14 days after release.
  • All snapshots not being no requested in the last 360 days will be automatically removed.

Getting a Nexus repository for your Project

File a ticket and specify what project you'd like a Nexus repo for.

3 repositories are typically created:

Projects can only publish to these repositories from their Jenkins instance. Committers cannot do anything administrative on the instance.

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 Jenkins ( to configure a job for deploying your artifacts.

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

Initial Maven POM setup

Before Jenkins 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 Jenkins instance is configured to use these IDs.

If you want to keep several snapshot versions use:


Note: this tag is ignored by Maven 3.x.

Jenkins Job Setup

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

There are 2 ways you might want to do this:

  1. Use the "deploy" goal as one of your Maven goals as part of your build. Be careful while doing that to not specify duplicate goals (e.g., mvn verify deploy will execute all phases up to verify twice).
  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. Example:

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 and your project cbi, then your Directory should be /jobs/genie.cbi/cbi-maven-plugins-build/workspace/. This setting should be configured in both your Build job and Deploy jobs.

Shared workspaces
This only applies to JIPP instances on our old infrastructure. Shared workspaces are not supported on our new cluster-based infrastructure.

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

Update 29.03.2017: This is not longer necessary when you want to deploy to or The credentials have been merged into the general Maven settings.xml file that all JIPPs are using.

Deploying a jar to

It is possible to use the Maven deploy:deploy-file goal to push a jar file into via Jenkins. 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="">

Configuring Jenkins 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.

Deploying to with Gradle

If you are using Gradle in your build job, you can also deploy to from your JIPP instance as described in the Gradle user guide.

Include in your gradle script authentication configuration using the settings below, e.g.

repositories {
  maven {
    credentials {
      username eclipseRepoUsername
      password eclipseRepoPassword
    authentication {

Webmaster will need to setup the Gradle plugin in your JIPP and provide ~/.gradle/ with the following two variables:


Please file a ticket for that.

Back to the top