New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resurrect OSGI support #1852
Comments
Hi, just to let you know, I have started working on this - especially on automated OSGi integration tests. I have created a repository for doing some experiments here. |
This sounds pretty good; I skimmed the code and I assume it does the right thing... Thanks for linking to the PaxExam page, it seems like it would do the job. Definitely submit a PR and let's try to integrate soon |
Ok, I will start with a PR (hopefully tomorrow) that re-enables the OSGi plugin and fixes the problem with the Require-Capability header. Then the build should again produce valid OSGi bundles. |
Revert "Re-enabled OSGi support (#1852)."
The commits that removed OSGi support are reverted. The Require-Capability header has been fixed.
The project currently contains a task to collect all dependencies and store them as jars in a dedicated folder. This is a prerequisite for the OSGi integration test, which needs to deploy all these jars as bundles.
This class uses PaxExam to deploy akka-http and all its dependencies in an Apache Felix OSGi container. It then creates a test HTTP server and interacts with it.
Future versions of Akka and Akka HTTP will not support OSGi. |
OSGI support regularly breaks during releasing (or even used to break the released artifacts without notice), which is the worst time for breakage. We therefore removed OSGI support while releasing 10.1.0-RC1.
If someone cares enough for OSGI support, please step up as a maintainer of Akka HTTP OSGI support. We'll need help with:
The text was updated successfully, but these errors were encountered: