This document summarises tagged Java-Runtime-Compiler releases from 2020-01-01 onwards, using the annotated Git tag dates and the commit history available on 2026-04-28.
The legacy compiler-* tags are included because they are the release tags used for the Maven artefact net.openhft:compiler.
Chronicle-wide release-note subscriptions remain available at https://chronicle.software/release-notes/.
The emphasis is on user-visible behaviour, compatibility, dependency alignment, security hardening, documentation, and operational impact.
Early-access releases are marked with ea in the version name.
The type marker uses ASCII rather than emoji to stay within the repository character-set policy:
-
[F] Functional- API, runtime behaviour, compiler behaviour, Java compatibility, diagnostics, packaging metadata, or security posture changed. -
[N] Non-functional- release alignment, dependency alignment, build, documentation, test, comment, or metadata changes only.
-
The latest tagged release in this window is
compiler-2026.2. It is primarily a Maven/BOM alignment release over2026.1. -
There are unreleased branch updates after
compiler-2026.2. The maindevelop/ealine contains the post-release snapshot reset plus documentation path fixes; separate feature and documentation branches contain JUnit 5 migration work and documentation clean-up. -
Runtime compilation became safer and more predictable across the 2020-2022 releases. Notable fixes include synchronised in-memory compiler buffers, safer concurrent
CachedCompiler.loadFromJavaexecution, Java 15 and Java 17 compatibility fixes, import/order race fixes, and customisable compiler options. -
The main functional upgrade path after the
2.4.xline is through the2.21ea*,2.23ea0,2.25ea3,2.26.x/2.27ea*, and2026.xreleases. Those releases add newer-JDK support, custom compiler options, file-manager customisation hooks, module metadata, and validation hardening. -
CachedCompilergained two file-manager extension paths. ThefileManagerOverridehook and publicMyJavaFileManagerconstructor were introduced incompiler-2.25ea3, andupdateFileManagerForClassLoader(ClassLoader, Consumer<MyJavaFileManager>)was added incompiler-2.27ea1and backported tocompiler-2.26.3. -
The
compiler-2026.0validation hardening is security-impacting. Generated class names are now checked before compilation or loading, generated source/class paths are resolved under their configured roots, and invalid traversal-like names fail earlier. Applications that deliberately generate unusual binary names should verify them before upgrading. -
JPMS and packaging metadata improved in the
2.26/2.27line.Automatic-Module-Namewas added for stable module naming, and the old distribution-management block was removed from the POM. -
Several releases are release-train or BOM alignment releases only. They are still listed because they are published artefacts, but their impact is described as dependency or build alignment rather than runtime behaviour.
| Date | Release | Main change | Benefit / impact |
|---|---|---|---|
2026-01-28 |
|
Aligned Maven versions to Chronicle BOM |
Use when aligning with the Chronicle |
2026-01-28 |
|
Aligned Maven versions to Chronicle BOM |
Provides release-train consistency for users consuming the Chronicle |
2026-01-28 |
|
Moved to calendar versioning and aligned to the |
Establishes the 2026 baseline. Upgrades get stronger validation around generated names and paths, better test coverage for runtime compilation, and current Chronicle release-train alignment. |
2025-10-30 |
|
Refreshed contributor guidance, licence text, README material, project requirements, Javadocs, and code comments; aligned the early-access BOM to |
Improves maintainability and documentation clarity for the |
2025-07-24 |
|
Updated the |
Use when remaining on the |
2025-07-23 |
|
Updated the |
Use when remaining on the |
2025-07-09 |
|
Updated parent/BOM versions and moved the third-party BOM away from references to a legacy staging repository URL. |
Keeps early-access dependency resolution current and avoids reliance on obsolete repository metadata. |
2025-03-12 |
|
Backported the ability to update the |
Allows callers and tests on the stable |
2025-03-12 |
|
Added |
Enables targeted file-manager updates per class loader, which is useful for advanced loading, testing, and cache-management scenarios. |
2024-11-15 |
|
Started the |
Provides a |
2024-11-15 |
|
Promoted the |
Gives module-path users a stable module name and provides the stable entry point for the |
2024-05-29 |
|
Started the |
Useful for consumers validating the |
2024-05-29 |
|
Promoted the |
Stable entry point for the |
2024-05-01 |
|
Added a |
Allows advanced users and tests to provide a custom file-manager implementation while preserving the normal compiler path for default users. |
2024-02-15 |
|
Updated parent/BOM versions for the |
Dependency alignment release; no user-facing runtime behaviour change was identified. |
2023-12-29 |
|
Fixed the current early-access version state and aligned to BOM |
Keeps the |
2023-11-24 |
|
Released the |
Provides a stable |
2023-11-24 |
|
Started the |
Release-train transition only; no major functional change over |
2023-10-25 |
|
Aligned parent/BOM versions, removed an unused import, refreshed copyright headers, and kept the project in line with the Chronicle ALL dependency set. |
Build and dependency alignment release for consumers following the |
2022-07-14 |
|
Added support for custom compiler options, moved to the standard Maven directory layout, removed the GitHub Actions workflow, and aligned Java 11/17 profile activation with the parent POM. |
Callers can now pass explicit compiler flags to |
2022-04-08 |
|
Fixed a |
Improves reliability for high-volume runtime compilation on Java 17. |
2021-12-22 |
|
Fixed Java 11+ test/runtime configuration issues, improved class import and class-loading order behaviour, added GitHub build metadata, and renamed the README to AsciiDoc. |
Improves correctness when generated classes depend on each other and makes the project easier to build and document on newer JDKs. |
2021-10-05 |
|
Improved Java 17 support, added a Java 11 build profile, fixed a Java 17 |
Reduces failures on Java 11/17 and keeps diagnostics consistent with Chronicle Core logging conventions. |
2021-03-16 |
|
Improved Azul Zing and Java 15 support, and aligned to BOM |
Broadens runtime support for non-standard JVM layouts and newer JDKs. |
2020-12-31 |
|
Started the |
Release-train transition from the |
2020-12-17 |
|
Made concurrent |
Reduces races and compiler-buffer corruption when several threads compile or load generated classes at the same time. |
2020-10-21 |
|
Added support for a generated method bridge used by Chronicle Wire MethodWriter/MethodReader mocking, added classpath handling for the Maven exec plugin, enabled Dependabot v2, and refreshed build dependencies. |
Supports back-to-back generated method-call testing scenarios and improves build/dependency maintenance. |
2020-06-19 |
|
Updated root POM, parent POM, third-party BOM, and Chronicle BOM versions for the |
Dependency alignment release for users staying on |
2020-01-31 |
|
Fixed in-memory file-manager buffer handling by using a synchronised map to avoid |
Improves runtime compilation reliability under concurrent or repeated generated-class workloads. |
The release history contains several release-train commits whose only effective change is Maven version alignment. Those releases are still listed because they are published artefacts, but their impact is intentionally described as dependency or build alignment rather than runtime behaviour.
When preparing future release notes, prefer summarising user impact rather than copying raw commit subjects. The most useful recurring categories are Java compatibility, class-loading behaviour, compiler/file-manager extension points, security validation, dependency/BOM alignment, packaging metadata, diagnostics, and documentation.