IKE Network

The IKE Network (Integrated Knowledge Exchange) is a sociotechnical fabric where knowledge compounds.

Foundation

The IKE foundation — published to Maven Central and inheritable by any project.

The foundation members fall into two layered orderings. ike-base-parent sits at the apex of the parent inheritance chain — every other foundation artifact inherits from it. ike-platform sits at the terminus of the build-and-release dependency chain — releases propagate through it last.

Build/release dependency order
Figure 1. Build/release dependency order

Members at the same level have no dependency on each other — ike-tooling and ike-workspace-extension can release in either order or in parallel.

IKE Base Parent

Maven Central[1]

Tier 0 foundation parent for the IKE Network — the apex of the parent inheritance forest, inherited by ike-tooling, ike-docs, and ike-platform. Carries shared publishing metadata, GPG signing, and Maven Central publishing configuration.

Version 15
Site ike.network/ike-base-parent[2]
GitHub IKE-Network/ike-base-parent[3]

IKE Java Support

Maven Central[4]

Shared, enforced-zero-dependency value types for the IKE Network: ConstantBackedEnum for compiler-visible constants, EnumDefinition for controlled-vocabulary enums, and the ReleasePolicy release-cascade policy ladder. See IKE-Network/ike-issues#498.

Version 9
Site ike.network/ike-java-support[5]
GitHub IKE-Network/ike-java-support[6]

IKE Tooling

Maven Central[7]

Workspace management, release orchestration, gitflow workflows, and build-time utilities for IKE Network projects.

Version 217
Site ike.network/ike-tooling[8]
GitHub IKE-Network/ike-tooling[9]

Modules

  • ike-build-standards
  • ike-workspace-model
  • ike-maven-plugin-support
  • ike-maven-plugin

IKE Docs

Maven Central[10]

Documentation plumbing for the IKE Network. Hosts the ike-doc-maven-plugin (ike-doc packaging, AsciiDoc/render pipeline, PDF dispatch), the Koncept AsciiDoc extension, DocBook XSL + fonts, shared doc resources, and the semantic linebreak reformatter. Split from ike-pipeline to resolve the extensions=true reactor-load cycle. See IKE-Network/ike-issues#216.

Version 67
Site ike.network/ike-docs[11]
GitHub IKE-Network/ike-docs[12]

Modules

  • ike-doc-resources
  • minimal-fonts
  • docbook-xsl
  • koncept-asciidoc-extension
  • ike-doc-maven-plugin
  • semantic-linebreak
  • ike-doc-ingest

IKE Workspace Extension

Maven Central[13]

Maven 4 build extension that prunes non-existent <subprojects> entries from workspace POMs before model validation. Lets a fresh clone of an IKE workspace bootstrap with mvn ws:scaffold-init before any subproject directory is on disk.

Version 9
Site ike.network/ike-workspace-extension[14]
GitHub IKE-Network/ike-workspace-extension[15]

IKE Version Management Extension

Maven Central[16]

Maven 4 build extension that implements the IKE typed-marker family for version-property naming: ${groupIdGAartifactIdVERSION}. Reads ALIAS properties from the inherited file-model and injects the declared short-name indirections, fails fast on undeclared canonical references, and detects ${G.A} typos with a corrective hint. Accepts the pre-#525 U+00B7 form during the transition. See IKE-Network/ike-issues#470, #472, #525, #526.

Version 10
Site ike.network/ike-version-management-extension[17]
GitHub IKE-Network/ike-version-management-extension[18]

IKE Platform

Maven Central[19]

Consumer-facing parent POM, BOM, and workspace management plugin for the IKE Network. External doc and code projects inherit from ike-parent (declared here); cross-repo workspace operations use ike-workspace-maven-plugin (ws:* goals). Consumes ike-docs as an external artifact — ike-parent declares ike-doc-maven-plugin with extensions=true, resolving from Nexus at project-load time. Split from the archived ike-pipeline; see IKE-Network/ike-issues#216.

Version 98
Site ike.network/ike-platform[20]
GitHub IKE-Network/ike-platform[21]

Modules

  • ike-parent
  • ike-workspace-maven-plugin
  • ike-bom

Examples

Reference projects that show how to consume the IKE foundation. They are deliberately not published to Maven Central: they are worked examples to read and copy, not libraries to depend on. Publishing them as artifacts would invite accidental coupling to code that exists only to illustrate a pattern.

IKE Documentation Example

Documentation-only project demonstrating the IKE AsciiDoc pipeline. Exercises all diagram types, Koncept macros, typography, and layout features across all 6 PDF renderers.

Version 33
Site ike.network/doc-example[22]
GitHub IKE-Network/doc-example[23]

HL7 IG Corpus Example

Worked example of the corpus-example pattern — multi-module documentation project that ingests a corpus of HL7 implementation guides into the IKE topic library and produces per-IG assemblies plus cross-IG analytic outputs.

Version 1
Site ike.network/hl7-ig-corpus-example[24]
GitHub IKE-Network/hl7-ig-corpus-example[25]

Modules

  • ingest
  • topics
  • corpus-guide
  • compendium
  • us-core
  • cross-ig-overlap

IKE Integration Tests Example

End-to-end smoke tests that exercise the IKE Network release cascade as external consumers would. Each IT case clones the intended usage pattern (doc-only project, java + docs, BOM import, ws:create scaffold) in a fresh Maven environment and asserts that the build succeeds and produces the expected artifacts.

Version 25
Site ike.network/integration-tests-example[26]
GitHub IKE-Network/integration-tests-example[27]

IKE Project Example

Example Java project demonstrating IKE documentation pipeline integration with Java source, tests, and Koncept macros.

Version 33
Site ike.network/project-example[28]
GitHub IKE-Network/project-example[29]

IKE Workspace Reactor Example

Version 24
Site ike.network/workspace-reactor-example[30]
GitHub IKE-Network/workspace-reactor-example[31]

Modules

  • doc-example
  • project-example
  • integration-tests-example
Searching...
No results.