What it provides

ike-base-parent carries the publishing-layer concerns shared by every IKE artifact, and nothing more — it is deliberately thin:

• Publishing metadata — developers, organization, license
• GPG artifact signing (Bouncy Castle signer)
• Maven Central deployment configuration (JReleaser)

Build conventions — Java version, compiler, test harness, enforcer — live in ike-parent, not here.

The parent tier

ike-base-parent              Tier 0  — this POM
   |-- ike-tooling           Tier 1
   |-- ike-docs              Tier 1
   `-- ike-platform          Tier 1
          `-- ike-parent     Tier 2  — consumer-facing parent
                 `-- consumers

ike-base-parent sits at the top of the release cascade and is published to Maven Central first, so every downstream POM’s parent chain resolves cleanly.

Coordinates

<parent>
    <groupId>network.ike</groupId>
    <artifactId>ike-base-parent</artifactId>
    <version>1</version>
</parent>

Available from Maven Central.

Projects inheriting ike-base-parent

• ike-tooling^[2] — Maven plugins and workspace tooling
• ike-docs^[3] — documentation plumbing
• ike-platform^[4] — consumer parent (ike-parent), BOM, workspace plugin