-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Bad and/or missing Require-Capability for osgi.serviceloader #6418
Comments
You don't seem to be using any component / bundle that has a
If you add such an entry, does the error/warning go away? (eg: add |
That is the strange thing, actually |
I've been able to reproduce the problem, investigating further. |
Signed-off-by: Jan Bartel <janb@webtide.com>
Yup, that there is a genuine bug. Fixing, see PR #6422 |
Jetty version(s)
Jetty Version 10.0.5
Java version/vendor
(use: java -version)
jdk16.0.1
OS type/version
Windows 10
Description
I'm trying to migrate our embedded jetty 9.4.x to jetty 10.0.5. I'm having a couple of OSGi and dependency issues.
To isolate the problem I created a simple OSGi Launch in Eclipse, having a couple bundles:
If I launch this settings I get the following validation error:
Require-Capability: osgi.serviceloader; filter:=“(osgi.serviceloader=org.eclipse.jetty.webapp.Configuration)”
PrintScreen: https://stackoverflow.com/questions/68004496/jetty-10-require-capability-osgi-serviceloader-filter-osgi-serviceloader-o
The text was updated successfully, but these errors were encountered: