Remove OSGi support #338
Merged
Remove OSGi support #338
Conversation
This file contains 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
This was referenced Nov 17, 2021
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.
I'm pretty sure no one is using the OSGi headers and the official Scala 3 JARs no longer have them. Various core projects in the ecosystem don't include them (e.g. cats, cats-effect). I suspect if there are any folks using OSGi with modern Scala libraries, they have a robust process for adding OSGi metadata as part of their build or container runtime.
Rather than continuing to copy/paste the same boilerplate in to every project and never test the result, let's remove it.
Please speak up if this is a concern! If folks are actively using OSGi metadata, I'm happy to keep it. I'll keep this PR open for a while to give folks a chance to chime in.