Repository navigation
Conversation
Add a public no-arg ResolverImpl constructor and register it in META-INF/services/org.osgi.service.resolver.Resolver, so tools can obtain the resolver without OSGi or a hard reference to the class. Showcase for the proposed OSGi spec change in osgi/org.osgi.service.resolver. No JIRA issue yet. 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.
Makes the Felix resolver discoverable with
java.util.ServiceLoader.ResolverImpl()constructor (error-level logging)META-INF/services/org.osgi.service.resolver.ResolverServiceLoaderTestThis is a showcase for the proposed OSGi spec change that requires resolvers to be discoverable via Java SPI (osgi/org.osgi.service.resolver#43).
The change is useful independently of that proposal: the spec does not forbid it, so it can be merged regardless of the OSGi outcome. Tools can then obtain the resolver without OSGi and without referencing the implementation class.
No JIRA issue yet; happy to create one if this is accepted.