You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: