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
Ensure all jetty modules that use ServiceLoader have correct OSGi manifest headers #2164
Comments
|
Depends on #2166 because spifly hardcodes use of asm 4 opcode, but the use of ServiceLoader in a static initializer requires asm 5 opcode. |
Signed-off-by: Jan Bartel <janb@webtide.com>
Signed-off-by: Jan Bartel <janb@webtide.com>
Signed-off-by: Jan Bartel <janb@webtide.com>
Signed-off-by: Jan Bartel <janb@webtide.com>
Signed-off-by: Jan Bartel <janb@webtide.com>
Signed-off-by: Jan Bartel <janb@webtide.com>
|
Merged to jetty-9.4 and above. |
|
This reintroduces 1365 as the osgi.serviceloader.processor is not optional and breaks eclipse help system as per https://bugs.eclipse.org/bugs/show_bug.cgi?id=532294 . Would you please make the requirement optional? |
|
If we can get a release with this issue fixed it would allow the release for Java 10 comptability of Eclipse Platform to ship compatible Jetty too. |
|
@akurtakov I submitted a PR to fix this for Eclipse's use-case. See #2377 |
This allows Eclipse to continue to make use of jetty-* bundles without requiring the presence of Apache Aries. This fixes a problem introduced by the resolution to #2164 and the same solution is used as in 10cdf16 See also the discussion at Eclipse: https://bugs.eclipse.org/bugs/show_bug.cgi?id=532294 Signed-off-by: Mat Booth <mat.booth@redhat.com>
Signed-off-by: Jan Bartel <janb@webtide.com>
Several jetty modules use the ServiceLoader these days, but they have not been updated to include the necessary manifest headers to ensure that the ServiceLoader will work in osgi.
Modules found so far that need attention:
The text was updated successfully, but these errors were encountered: