Skip to content

Expose Maven logging output capabilities in Maven 3.10 - #13209

Draft
wilx wants to merge 1 commit into
apache:maven-3.10.xfrom
wilx:output-capabilities-3.10
Draft

wilx wants to merge 1 commit into
apache:maven-3.10.xfrom
wilx:output-capabilities-3.10

Conversation

@wilx

@wilx wilx commented Sep 20, 2026

Copy link
Copy Markdown
Contributor

Give plugins the logging destination and encoding through an injectable OutputCapabilities service and an immutable maven.logging.outputCapabilities map in execution-request data. Plugins compiled against older Maven APIs can read the map without reflection.

Capture the activated logger's actual route, including file-open fallback; ambiguous terminal probes remain UNKNOWN. Existing routing and encoding are preserved. Maven 3.10 counterpart of #13208.

Validation: reactor verification, focused Core ITs including forced color, and Linux runtime/encoding checks passed. macOS and Windows remain untested.

Provide a singleton service describing the current logging destination and
charset, plus an immutable execution-request data map for plugins compiled
against older Maven APIs. Capture the map at the start of every Maven
execution, preserving retained maps through request reuse and cleanup.

Capture the actual logging route, preserve initialization and cleanup
behavior, and treat negative exec-provider probes as unknown. Cover
injection, request compatibility access, resident lifecycle where supported,
and terminal detection.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant