Release: internal modules (ui/examples/codegen) reach Maven Central

[alexmond]

The central-publishing-maven-plugin ignores maven.deploy.skip (that property only governs the stock maven-deploy-plugin, which this plugin replaces), so a multi-module reactor publishes every module to Maven Central — including internal ones (examples / codegen) that are not libraries.

It is an aggregator extension uploading one bundle in the context of the last reactor module, so per-module <skipPublishing> would risk skipping the whole upload. The safe lever is excludeArtifacts on the parent central-publishing config (read once on the aggregator; drops just the named artifactId(s) while still publishing the real libraries). Already-released versions on Central are immutable; this affects future releases. Same issue diagnosed/fixed in alexmond/jvmlens#117 / alexmond/jvmlens#118.

This repo

These are codegen / examples, not libraries — not yet on Central, but nothing excludes them, so the next release will publish them:

• jsupervisor-examples
• jsupervisor-apicdoc-gen
• jsupervisor-apiclient-gen

(jsupervisor-ui is a published artifact — leave it. The -core/-rest/-apiclient libraries and -cli are fine too.)

Fix

<configuration>
  <!-- existing config … -->
  <excludeArtifacts>
    <excludeArtifact>jsupervisor-examples</excludeArtifact>
    <excludeArtifact>jsupervisor-apicdoc-gen</excludeArtifact>
    <excludeArtifact>jsupervisor-apiclient-gen</excludeArtifact>
  </excludeArtifacts>
</configuration>