Skip to content

Developer Guide

Jump to bottom
Daniel Burrell edited this page Dec 12, 2015 · 1 revision

Publishing artifacts to Maven central.

A step by step guide to publishing new versions of this library to maven.

##Prerequisites Confirm that gpg is installed by checking the version at the Git Shell prompt:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

D:\Users\terabyte> gpg --version

Expected output:

gpg (GnuPG) 2.0.26 (Gpg4win 2.2.2)
libgcrypt 1.6.1
Copyright (C) 2013 Free Software Foundation, Inc.
...

Confirm the developer keys have been imported at the Git Shell prompt:

gpg --list-keys

Expected output:

D:\Users\terabyte> gpg --list-keys
pub   2048R/E76B7011 2014-11-15
uid       [ultimate] Daniel Burrell (Release Owner) <[email protected]>
....

If you don't see the keys present, install Kleopatra, then import the keys from secure storage.

Confirm your settings file is present and contains the correct login information:

D:\Users\username\.m2\settings.xml

<settings>
  <servers>
    <server>
      <id>ossrh</id>
      <username>sonatypeusername</username>
      <password>sonatypepassword</password>
    </server>
  </servers>
</settings>

Confirm an external Maven installation is present on the Path variable:

mvn --version

Expected Output:

Apache Maven 3.2.3 (xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx; 2014-08-11T21:58:1
0+01:00)
Maven home: D:\apache-maven-3.2.3\bin\..
Java version: 1.8.xxxx, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.xxxx\jre
Default locale: en_GB, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"

If not, download and install maven to this directory D:\apache-maven-3.2.3 and add it to the windows PATH variable so that running the version check above works.

Before Publishing

Ensure that your changes have been committed to Git in full, with a -SNAPSHOT tag. In the event of a build failure in the instructions below, delete the backup, set the -SNAPSHOT to be what it was, recommit and retry.

Publishing

At the git shell, cd into the project directory (workspace\angular-spring-archetype) and execute the following commands (accepting all the defaults by pressing enter when prompted):

mvn clean deploy
mvn release:clean release:prepare
mvn release:perform

This will publish the artifact, solidify the release tag, and increment the snapshot number. Be sure to recommit the new snapshot to git afterwards.

Artifacts

Artifacts can be managed at https://oss.sonatype.org/

Clone this wiki locally