Vidocq is intentionally split into independent projects instead of one giant release train.
Each brick has a clear scope, a dedicated release cycle, and minimal coupling:
-
foundational modules (
chappe,vauban,champollion,ravel), -
Jakarta layers (
foy,cassini), -
MicroProfile implementations and integration layers,
-
runtime orchestration in
vidocq.
This design gives us better control over quality and publication:
-
we can release stable foundations earlier,
-
we can iterate faster on higher layers without blocking everything,
-
users can consume only what they need.
The publication order on Maven Central follows that same dependency graph.
