[
https://issues.apache.org/jira/browse/SM-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318911#comment-17318911
]
Freeman Yue Fang commented on SM-4727:
--------------------------------------
Right, there's actually a split-package(OSGi term) issue between annotation-api
and jsr305 bundles(two bundles both have javax.annotation package), and what
opensaml needs is the jsr305 one, so package start from 3 can avoid such issue.
Fixed accordingly.
Thanks!
Freeman
> [opensaml] Invalid range for javax.annotation import
> ----------------------------------------------------
>
> Key: SM-4727
> URL: https://issues.apache.org/jira/browse/SM-4727
> Project: ServiceMix
> Issue Type: Bug
> Components: bundles
> Reporter: Arnaud MERGEY
> Assignee: Freeman Yue Fang
> Priority: Major
> Fix For: bundles-2021.04
>
>
> opensaml 3.4.6 is importing javax annotation with this range version 1 to
> version 4 while it depends on jsr305 (javax.annotation 3)
> javax.annotation v1 corresponds to jee annotation (jakarta.annotation-api)
> which completely unrelated to jsr305 (even if they share same package name
> which is a shame but that's another story)
> I am not sure it is really a big deal as jsr305 are not supposed to be
> retained at runtime, but there could be some strange wiring effects. I think
> javax.annotation shoud be from v3 to v4 for open saml (and maybe set as
> optional) instead of
> {code:java}
> javax.annotation;version="[1,4)",{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
