Skip to content
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

jersey-common doesn't specify javax.annotation version in manifest #4156

Closed
cliffred opened this issue Jun 11, 2019 · 3 comments
Closed

jersey-common doesn't specify javax.annotation version in manifest #4156

cliffred opened this issue Jun 11, 2019 · 3 comments

Comments

@cliffred
Copy link

Since version 2.28, jersey-common does not specify a version number in the Import-Package for javax.annotation in the manifest anymore. This leads to a problem in an OSGi environment (An Eclipse RCP application in my case); javax.annotation is resolved to the system bundle instead of jakarta.annotation-api leading to a java.lang.NoClassDefFoundError: javax/annotation/Priority at runtime. Manually editing the manifest by spicifying a version like javax.annotation;version="[1.3,2)" fixes the problem.

@jansupol
Copy link
Contributor

The version was removed so that the JDK's annotation is used. Unfortunately, the Priority is not in the package. We should fix the version.

@jansupol
Copy link
Contributor

Priority is since Common Annotations 1.2

@jansupol
Copy link
Contributor

Fixed by #4164

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants