Personal Parent POM
Find a file
Paul Campbell d3eec22e46
Update signing keys (#133)
* Use GitHub Actions

* Update codesigning keys
2020-03-16 15:19:41 +00:00
.github Update signing keys (#133) 2020-03-16 15:19:41 +00:00
.travis-support@de2613446f Update signing keys (#133) 2020-03-16 15:19:41 +00:00
.gitignore Update signing keys (#133) 2020-03-16 15:19:41 +00:00
.gitmodules Update signing keys (#133) 2020-03-16 15:19:41 +00:00
.travis.yml Update signing keys (#133) 2020-03-16 15:19:41 +00:00
CHANGELOG Fix badge links in README (#115) 2018-10-07 20:12:25 +01:00
LICENSE.txt LICENSE.txt: added - required by kemitix-checkstyle-ruleset 2016-09-11 18:15:33 +01:00
lombok.config lombok.config: added to prevent generated annotation 2018-03-04 18:06:12 +00:00
pom.xml Update signing keys (#133) 2020-03-16 15:19:41 +00:00
README.org Fix badge links in README (#115) 2018-10-07 20:12:25 +01:00

KEMITIX-PARENT

Usage

Use as a parent pom.

  <parent>
    <groupId>net.kemitix</groupId>
    <artifactId>kemitix-parent</artifactId>
    <version>RELEASE</version>
  </parent>

Contents

The POM defines the following items:

  • issueManagement
  • scm
  • url
  • inceptionYear
  • licenses
  • developers In your child pom you should override, at least, the issueManagement, scm, url and inceptionYear sections.

Properties

The POM sets the following properties:

  • project.reporting.outputEncoding as UTF-8
  • java.version as 1.8

Profile release

The release profile is for use when deploying your project.

It configures the following plugins:

maven-javadoc-plugin

Executes the jar goal during the package phase.

maven-source-plugin

Executes the jar-no-fork goal during the package phase.

maven-gpg-plugin

Executes the sign goal during the package phase.

The default gpg key will be used with the password defined in the gpg.passphrase property.

maven-deploy-plugin

This plugin is configured to not run. Deployment, uploading of artifacts, is handled by the nexus-staging-maven-plugin.

nexus-staging-maven-plugin

Executes the default goals.

Uploads artifacts to the Sonatype Nexus server, https://oss.sonatype.org/, leaving the artifacts in the Staging repository. From there they will need to be released manually.

Authentication details are taken from the sonatype-nexus server in your settings.xml file.

Distribution Management

The Nexus Sonatype repositories are declared within distributionManagement.