Skip to content

docs(adr): correct ADR 0016 to the shipped 2.0 module layout #395

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
DemchaAV merged 2 commits into from
Jul 13, 2026
Merged

docs(adr): correct ADR 0016 to the shipped 2.0 module layout #395

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7979ccd
docs(adr): correct ADR 0016 to the shipped 2.0 module layout
DemchaAV Jul 13, 2026
cce49b3
Merge branch 'develop' into harden/adr-0016-accuracy
DemchaAV Jul 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 9 additions & 6 deletions docs/adr/0016-multi-module-packaging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,9 +60,10 @@ render backends discovered at runtime through a `ServiceLoader` SPI.
(via the wrapper) + templates + the independently-versioned `graph-compose-fonts` and
`graph-compose-emoji` companions. Office backends are not bundled.

The engine sources stay at the repository root and only the **root coordinate** is
renamed `graph-compose` → `graph-compose-core`; the new wrapper is a small module. The
default coordinate `graph-compose` therefore continues to mean "PDF out of the box".
The engine sources live in the `core/` module under the coordinate `graph-compose-core`;
the repository root is the `graph-compose-build` aggregator pom that binds the modules
into one lockstep reactor, and `graph-compose` is the small jar-wrapper. The default
coordinate `graph-compose` therefore continues to mean "PDF out of the box".

No JPMS: modules carry an `Automatic-Module-Name` only, so a split package across
test-scope jars stays legal on the classpath.
Expand All @@ -82,6 +83,8 @@ test-scope jars stays legal on the classpath.
`graph-compose-emoji` keep their own lines (they change rarely).
- **A `MissingBackendException` is now the "why won't it render" signal** for a lean
`graph-compose-core`, replacing the pre-split assumption that the backend is always present.
- The legacy `Entity`-Component-System render pipeline moves into `graph-compose-render-pdf`
rather than being deleted; it is dead on the canonical path but still exercised by
test scaffolding, so its removal is deferred beyond 2.0.
- The dormant `Entity`-Component-System engine internals — the `EntityManager` /
`SystemECS` runtime, the `Entity` component model, and the ECS render pipeline —
were removed in 2.0.0 rather than carried into a module. They were unreachable from
the live `DocumentSession` → layout compiler → fixed-layout backend path, so document
layout, PDF output, and the public `guideLines(...)` overlay are unchanged.
Loading