Skip to content

⭐ Divergences From Upstream

Jump to bottom
Terrence Daniels edited this page Aug 24, 2026 · 2 revisions

Every place this fork's behavior deliberately doesn't match upstream Axon Framework, gathered in one place so none of them read as an oversight:

  • Java 25 toolchain, not upstream's Java 21 floor — raises the minimum JDK needed to consume this fork's published artifacts
  • Checkstyle bans org.springframework.lang.Nullable in addition to upstream's NonNull-only ban, completing a pairing every other framework in the list already had
  • integrationtests doesn't publish to Maven Central — upstream doesn't skip-publish it either, which looks like an oversight on upstream's part rather than a choice
  • POM metadata (SCM, developers, organization) points at this fork's own repo and maintainer, not upstream's AxonIQ organization or named developers — the jar manifest's Implementation-Vendor follows the same rule (caught pointing at upstream's AxonIQ B.V. on a routine re-read, since addDefaultImplementationEntries derives it separately from the POM's own metadata)
  • No gradle/libs.versions.toml version catalog — see Versioning Approach

Each of these is explained in more depth in todo.md.

Clone this wiki locally