gnodet opened a new pull request, #13700: URL: https://github.com/apache/maven/pull/13700
## Summary This PR cherry-picks the build-report feature commits from PR #12695 onto the `feature/unified-logging-api` branch, adapting them to the 3-jar split logging architecture introduced there. ## What's included - **Structured build report** (`target/build-report.json`) capturing per-module and per-mojo execution details, timing, and captured log lines - **Report versioning** (`reportVersion` field added to the JSON schema) - **Trace correlation IDs** for module and mojo reports (#13627) ## Architecture adaptations (vs PR #12695) The original PR targeted `master` where the logging stack was a single jar. The `feature/unified-logging-api` branch splits it into `maven-api-log`, `maven-logging`, `maven-logging-slf4j`, and `maven-logging-jul`. The following adaptations were made: 1. **Build report API types moved to `maven-api-core/build/report/`** — `BuildReport`, `BuildStatus`, `FailureReport`, `ModuleReport`, `MojoReport` belong in `maven-api-core` (they reference `BuildInvocation` and `BuilderProblem` from core, not logging types). They are **not** in `maven-api-log`. 2. **`BuildEnvironment` → `BuildInvocation`** — the original PR's first commit added `BuildEnvironment` to `Session`; the `feature/unified-logging-api` branch already has the equivalent as `BuildInvocation`. All references updated accordingly. 3. **Sink-routing tests updated** — `MavenSimpleLoggerTest` rewrote the sink tests to use `LoggerManager.get().setLogSink()` with the new `LogEvent`-based `LogSink` API (instead of the old `MavenSimpleLogger.LogSink` inner interface). 4. **`SessionStub` updated** — `buildEnvironment()` replaced with `buildInvocation()` returning a `BuildInvocation` stub. ## Testing ``` mvn test -pl impl/maven-logging,impl/maven-logging-slf4j,impl/maven-logging-jul,impl/maven-core -am ``` All tests pass (832 tests, 0 failures, 1 skipped). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
