Conversation
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.
Draft
1 task
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Maven 4.0 counterpart of #13208: expose logging destination and encoding through an injectable
OutputCapabilitiesservice and an immutablemaven.logging.outputCapabilitiesmap in execution-request data for older plugins.Capture the selected logging route, retain conservative
UNKNOWNresults, and support resident-invocation restoration without changing routing or encoding.Validation: reactor verification, focused Core ITs, Java 17 CLI/resident tests, and Linux runtime/encoding checks passed. macOS and Windows remain untested.