Snapshot Release Process

Apache Isis consists of a number of separately releasable modules; see the main release process documentation for full details. All the non-core components depend on the core, and use the core's parent pom.xml as their parent pom.

Prerequisites

Before you start, make sure you've defined the snapshots repo in your local ~/.m2/settings.xml file:

<settings>
  <servers>
    <!-- To publish a snapshot of some part of Maven -->
    <server>
      <id>apache.snapshots.https</id>
      <username>xxxxxxx</username>
      <password>yyyyyyy</password>
    </server>
    ...
  </servers>
  ...
</settings>

where xxxxxxx and yyyyyyy are your Apache LDAP username and password. For more information, see these ASF docs.

Sanity Check

Before deploying the snapshot, perform a quick sanity check.

First, delete all Isis artifacts from your local Maven repo:

rm -rf ~/.m2/repository/org/apache/isis

Next, check that the releasable module builds independently. The build process depends on whether the artifact is of Isis core or of one of its components:

• For Isis core, build using the -o offline flag:

  mvn clean install -o

  Confirm that the versions of the Isis artifacts now cached in your local repository are correct.

• For an Isis component, build without the offline flag; Maven should pull down the component's dependencies from the Maven central repo:

  mvn clean install

  Confirm that the versions of the Isis artifacts now cached in your local repository are correct (both those pulled down from Maven central repo, as well as those of the component built locally).

Deploy All Modules

Deploy all modules using:

mvn -D deploy=snapshot deploy

This will deploy all the modules that make up a release.

To confirm that they are present, browse to Apache's Nexus repository manager and search for "isis".