There is an incompatibility between the Apache maven-gpg-plugin configured in the jboss-parent pom and the Sonatype nxrm3-maven-plugin that we will need to use to do staged maven deployments once JBoss Nexus moves to Maven 3.

I've proposed fixes to both the Apache maven-gpg-plugin and the Sonatype nxrm3-maven-plugin repos, but until one of those is incorporated in a release, or some other fix is released, we need to work around this within the WildFly org.

The problem happens if a maven module build uses the maven-assembly-plugin to attach an artifact to the build, but configures the plugin not to add a classifier for the artifact. WildFly projects do this routinely in modules related to building feature packs or creating dists. We can't change this to add classifiers as that would break the consumers of these artifacts.

For the feature pack building use cases I've created some workarounds, but unfortunately they don't work for the dist building uses. The only option I could see for those was to fork the maven-gpg-plugin and create a release that has the fix I proposed to Apache.

https://github.com/wildfly/wildfly-maven-gpg-plugin/releases/tag/wildfly-maven-gpg-plugin-3.2.7.SP1

The task here is to override the jboss-parent pom's gpg-sign profile to disable execution of the Apache plugin and instead use the fork.

Timing: We need to do this before our first release to a Nexus 3 based JBoss Nexus. AIUI we will get at least a week's notice before that switch occurs.

Background:

The proposed Apache fix: https://github.com/apache/maven-gpg-plugin/pull/135

The proposed Sonatype fix: https://github.com/sonatype/nxrm3-maven-plugin/pull/45