You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Francois Papon (JIRA)" <ji...@apache.org> on 2019/01/13 15:56:00 UTC
[jira] [Updated] (SHIRO-655) shiro-core has an undesirable runtime
OSGi dependency to spring-beans
[ https://issues.apache.org/jira/browse/SHIRO-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francois Papon updated SHIRO-655:
---------------------------------
Fix Version/s: 1.4.1
> shiro-core has an undesirable runtime OSGi dependency to spring-beans
> ---------------------------------------------------------------------
>
> Key: SHIRO-655
> URL: https://issues.apache.org/jira/browse/SHIRO-655
> Project: Shiro
> Issue Type: Bug
> Affects Versions: 1.4.0-RC2
> Reporter: Steinar Bang
> Assignee: Francois Papon
> Priority: Major
> Labels: OSGi, osgi
> Fix For: 1.4.1
>
>
> The manifest.mf of the shiro-core jar has a runtime dependency on org.apache.commons.configuration2.interpol,
> The org.apache.commons.configuration2.interpol package is provided by
> {code:xml}
> <dependency>
> <groupId>org.apache.commons</groupId>
> <artifactId>commons-configuration2</artifactId>
> <version>2.1</version>
> <scope>compile</scope>
> </dependency>
> {code}
> and this bundle (it *is* a bundle with an OSGi MANIFEST.MF) has springframework package requirements in the Import-Package header:
> {noformat}
> org.springframework.beans.factory,
> org.springframework.core.env,
> org.springframework.core.io,
> org.springframework.util
> {noformat}
> It should be possible to fix this by bumping the config-configurations2 dependency to to 2.2, for in that version of the bundle, the springframework packages are made optional (and the runtime requirement goes away).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)