[
https://issues.apache.org/jira/browse/SHIRO-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359134#comment-15359134
]
Brian Demers commented on SHIRO-502:
------------------------------------
[~mcculls] I'll merge this into 1.3, but, a question for you...
We have a few of these issues open, and I'm guessing this stems from not having
good way to test the bundle metadata.
Is there an _easy_ way we can test the metadata? Or should we just do what
servicemix does and deal with bundling outside of this project (so the imports
can be adjusted independent of this project)
> OSGi import of com.google.inject in shiro-guice has incorrect version range
> ---------------------------------------------------------------------------
>
> Key: SHIRO-502
> URL: https://issues.apache.org/jira/browse/SHIRO-502
> Project: Shiro
> Issue Type: Bug
> Components: Integration: Guice
> Reporter: Stuart McCulloch
> Assignee: Jared Bunting
> Labels: patch
> Attachments: SHIRO-502.patch
>
>
> The guice project follows a relaxed* form of semantic versioning in its
> package exports. So while the bundle version increases on each major release:
> 2, 3, 4 the exported package version only increases the minor segment: 1.2,
> 1.3, 1.4 to reflect that the API is still binary compatible - albeit with
> additional features.
> (* relaxed because the same version is applied to all packages in the bundle)
> This means that shiro-guice fails to resolve against the official guice
> bundle, because guice 3 is exporting com.google.inject with a version "1.3",
> but shiro-guice is importing com.google.inject with a range of "\[3, 4)"
> Solution is to either remove the version range on the import, or widen it to
> something like "1.3" (ie. provide a lower bound, but not an upper bound).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
