Cross-repository paths

Latest stable Based on Javers release 0.2.1

The JaVers manual intentionally stops where another repository owns the generic contract.

Exposed boundary

javers-exposed persists JaVers CDO snapshots and commit metadata. It does not replace JDBC/R2DBC application repositories, transaction helpers, cache write modes, Ktor helpers, or Spring auto-configuration from bluetape4k-exposed. Use the published Exposed manual for those topics, especially transaction ownership.

Projects boundary

Redis clients, Kafka utilities, codecs, DDD foundations outside the JaVers workflow, and Testcontainers launchers belong to bluetape4k-projects. Use its published manual. This repository’s release example directly uses Projects facilities in examples/javers-exposed-ddd/build.gradle.kts.

Version boundary

Consumers should import one io.github.bluetape4k:bluetape4k-dependencies ecosystem version. That platform coordinates Projects, Exposed, Redis, Kafka, and Javers artifacts. Do not construct a compatibility matrix inside an application build unless the ecosystem platform is unavailable.

Ktor integration, Spring Boot 4 auto-configuration, examples/javers-ktor, examples/javers-spring-boot4, and benchmark/javers-exposed-benchmark are after 0.2.1. Their current develop source must not be read as a 0.2 contract. The release module boundary is visible in settings.gradle.kts.