Build tooling for the IKE Network: workspace management, release orchestration, gitflow workflows, and build-time utilities.
| Module | Artifact | Purpose |
|---|---|---|
ike-build-standards |
network.ike.tooling:ike-build-standards |
Versioned reference material (Claude standards, configs, scaffold manifest) — multi-classifier ZIP artifact |
ike-workspace-model |
network.ike.tooling:ike-workspace-model |
Data model and conventions for an IKE workspace; shared by both Maven plugins |
ike-maven-plugin-support |
network.ike.tooling:ike-maven-plugin-support |
Helper library for IKE Maven plugins (goal registry, base mojo, parameter parsing) |
ike-maven-plugin |
network.ike.tooling:ike-maven-plugin |
ike:* goals — release orchestration, scaffolding, site deploy, version upgrades |
mvn clean install[ike-tooling] → ike-docs → ike-platform → { doc-example, project-example, integration-tests-example, workspace-reactor-example }
ike-tooling releases first because both ike-docs and ike-platform
declare ike-maven-plugin in their <pluginManagement> (via
${ike-tooling.version}) and consume ike-build-standards at
validate time. Those artifacts must be resolvable from Nexus
when the downstream reactors load.
The cascade ordering is structurally upstream-first; it is not
driven by extension-realm timing. Earlier revisions cited
<extensions>true</extensions> for <packaging>ike-doc</packaging>
as the reason — that machinery was retired in
IKE-Network/ike-issues#321
when ike-doc-maven-plugin adopted a classifier-canonical doc
shape (<classifier>adoc</classifier><type>zip</type>). The
ordering is unchanged; the literal-version pinning is gone.
The cascade is orchestrated by ike:release-cascade, which assembles
the order from each foundation repo's own
src/main/cascade/release-cascade.yaml
(IKE-Network/ike-issues#420).
How the release cascade works — the decentralized manifest model,
the ike:release-cascade / ike:cascade-export goals, and how to
test and run it — is documented in
The IKE Release Cascade
(ike-maven-plugin site). The full step-by-step release procedure is
in cutting-a-release.adoc.
ike-tooling is the source of the IKE Network's doc-as-code
infrastructure. Its ike-build-standards
submodule ships every build convention, documentation standard,
and AI-assistant instruction as versioned Markdown files. The
claude classifier ZIP is unpacked into every consuming project's
.claude/standards/ directory at validate phase — so when a
developer or Claude itself opens an IKE project, the agent reads
the standards locally and applies them automatically; contributors
don't have to memorize the conventions.
See the ike-build-standards README
for the inventory of standards (each is a linkable Markdown file
covering one topic: MAVEN.md, IKE-DOC.md, IKE-DIAGRAMS.md,
IKE-RELEASE.md, etc.) and the
published index.
- Documentation:
https://ike.network/ike-tooling/ - Build standards:
ike-build-standards - Issues:
IKE-Network/ike-issues(cross-project tracker) - Source:
IKE-Network/ike-tooling