New in the 0.3.0 development line — everything listed here landed after the 0.3.0 release and is not part of it. Sections carrying the NEW badge across the documentation point to these features. When the next release train ships, this page is frozen with it and restarts empty on the dev line.
Runtime
-
NEW
vidocq:modularizeMaven goal — generates build-time module descriptors for non-modular dependencies, so third-party classpath jars fit the strict Java Modules graph. See the Maven plugin page. -
NEW 1868 official MicroProfile 7.1 TCK tests green on the assembled runtime — all eight component specs, run through the in-reactor
-Ptckrunners. Jakarta Core Profile 11 certification is in preparation (composite TCK 10/13 on JDK 25). See the TCK page. -
NEW
vidocq:check-module-info/complete-module-info— consumermodule-info.javaverification rolled out reactor-wide. -
CLI hotfixes
0.2.1→0.2.3(scaffolding fixes;vidocq createstill pins the released0.3.0parent).
Dependency injection — Vauban
-
NEW Client-proxy weaving tiers — a normal-scoped bean without a usable no-arg constructor gets its
ProxyLinkentry constructor woven automatically atprocess-classes, with a clear unproxyable-bean diagnostic. See Vauban internals.
Persistence — Mansart
-
NEW Named datasources routing actually works end to end — on 0.2.0,
@Repository(dataStore = "…")silently hit the default datasource (MANSART-005); the dev line routes it to its named pool (vidocq.pool.<name>.*), pairing with the PostgreSQL Dev Services one-container-per-datasource provisioning. See Mansart usage.
New brick
-
NEW Erasmus — Jakarta Validation 3.1 implementation, in development (engine, the 21 built-in constraints, custom/composed constraints, interpolation). Not released yet. See the Erasmus docs.