Skip to content


Repository files navigation


Maven Central Maven Central (snapshot) Codecov Java Version


JVM Platform Status
OpenJDK (Temurin) Current Linux Build (OpenJDK (Temurin) Current, Linux)
OpenJDK (Temurin) LTS Linux Build (OpenJDK (Temurin) LTS, Linux)
OpenJDK (Temurin) Current Windows Build (OpenJDK (Temurin) Current, Windows)
OpenJDK (Temurin) LTS Windows Build (OpenJDK (Temurin) LTS, Windows)


To build this project, you must use:

$ mvn -Denforcer.skip=true clean package

The reason for this is that this POM file is intended to be the root POM for io7m projects and uses the Maven Enforcer plugin to require that descendant projects define values for certain properties that this root POM leaves empty. Because there is no way in Maven to have a plugin applied only to descendants, the root POM actually cannot pass its own checks! Using the enforcer.skip property allows the root POM to be installed and deployed to repositories.


The primogenitor POM builds on existing Maven conventions and enforces stricter conventions of its own. The POM is heavily commented and exposes several configurable properties. See the properties section in the POM for details.

The primogenitor POM is heavily biased towards extensive static checking, and the production of byte-for-byte reproducible builds.

By setting the parent of a project's POM file to com.io7m.primogenitor, the project receives the following services:

  • Generation of CycloneDX SBOMs.
  • Enforcement of the presence of POM properties required for Maven Central: Descendant POMs are required to provide description, url, and name elements.
  • Enforcement of a minimum Java version (currently 21) with a friendly error message if the project is built on a JDK that is too old.
  • Enforcement of a minimum Maven version (currently 3.8.2) with a friendly error message if the project is built with a version of Maven that is too old.
  • The immediate rejection of circular dependencies.
  • Enforcement of reproducible builds: No (transitive) dependency may depend on a SNAPSHOT version.
  • Enforcement of plugin versioning: No plugin may be added without an explicit version number.
  • Insertion of Git commit identifiers into the produced Jar file Implementation-Build manifest field with the buildnumber-maven-plugin. This assists with tracing exactly which artifacts were used to produce an application.
  • Byte-for-byte reproducible Jar files with the reproducible-build-maven-plugin. This may fail:
    • For JavaDoc jars, as the output of the javadoc tool is not deterministic.
    • If the project adds extra plugins that insert non-reproducible content into Jar files.
    • For SNAPSHOT versions of projects, as this will often result in various tools inserting the snapshot date and time into the Jar content.
  • Automatic insertion of OSGi metadata into the produced Jar files using the bnd-maven-plugin. Sensible default values are chosen based on metadata given in the POM file, and this can be overridden on a per-module basis.
  • Automatic checking of semantic versioning using the bnd-baseline-maven-plugin. Bytecode is analyzed and the build fails if, for example, binary incompatible changes have been made without incrementing the project's major version number.
  • Automatic source style checks using Checkstyle. Rules are consulted from external Maven artifacts in order to facilitate sharing rules across large numbers of projects and enforcing a consistent style everywhere.
  • Automated bug-checking with SpotBugs. The build fails if probable bugs are found.
  • Automatic production of JavaDoc and -sources Jar files, sufficient for publishing to Maven Central.
  • Automatic signing of artifacts with the maven-gpg-plugin, sufficient for publishing to Maven Central.
  • Incorporation of the nexus-staging-maven-plugin for publishing releases to Maven Central with a single mvn clean deploy command.
  • Analysis of dependency issues (unused dependencies, undeclared but used transitive dependencies) with the maven-dependency-plugin. The build fails if any dependency issues are discovered.
  • Generation of minimalist single page sites with minisite.
  • Automatic collection of code coverage information with JaCoCo.
  • All plugin versions are specified with Maven properties, and can therefore be overridden in the (unfortunate) case of a plugin being buggy, and can be efficiently updated with the versions-maven-plugin.
  • The ability to turn off all optional features and produce a build as quickly as possible by setting the property io7m.quickBuild to true on the command line: $ mvn -Dio7m.quickBuild=true clean package.
  • The ability to conveniently deploy to an alternate repository using properties. If the io7m.useAlternateRepository property is set, then deployment of releases will use a repository with id ${} and URL ${io7m.repository.releases.url}, and deployment of snapshots will use a repository with id ${} and URL ${io7m.repository.snapshots.url}. The intention is that these properties will be set within a profile in the user's ~/.m2/settings.xml file, or passed on the command line.