Repository navigation
Conversation
ResolveContext.getLogger() returns an Optional<FormatterLogger>, empty by default, so resolve contexts can observe a resolve operation. FormatterLogger needs no logging framework to implement. - Document the Logging section and import ranges in the spec - Bump org.osgi.service.resolver to 1.2.0 - Add org.osgi.service.log to the API and TCK run dependencies Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This was referenced Oct 29, 2026
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
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.
Moved from osgi/osgi#883, using
FormatterLoggeras agreed in the discussion.A resolve operation is a black box: callers only see wires or a
ResolutionException.Changes
ResolveContext.getLogger()returns anOptional<FormatterLogger>, empty by default. The resolver may use the logger but is not required to.LoggerFactoryis used, provider range if the context supplies its ownFormatterLogger.org.osgi.service.log1.4 dependency.No TCK test, because the resolver is not required to log.
Proof of feasibility: apache/felix-dev#585 (stacked on apache/felix-dev#584). A resolver created through the SPI (#43) has no other way to get a logger, because it needs a no-arg constructor.