Hi Steinar, FYI, as said, I'm working on a complete Karaf 4 update for Shiro (discussed with Shiro guys and François).
I will keep you posted. Regards JB On 25/11/2018 11:59, Steinar Bang wrote: >>>>>> Steinar Bang <[email protected]>: >>>>>> Steinar Bang <[email protected]>: >>> Problems so far: >>> 1. shiro-core requires spring-beans in a manifest.mf import-package, in >>> addition to being an extra dependency, spring-beans and its >>> dependencies aren't OSGi bundles, so karaf needs to wrap them > >> I reported this as a JIRA issue and provided a pull request to fix it >> https://issues.apache.org/jira/browse/SHIRO-655 > >> It's an indirect runtime dependency: shiro-core depends on packages from >> commons-configuration2 2.1, which in its MANIFEST.MF has non-optional >> dependencies on springframework packages. > >> The fix in the PR is a version bump of commons-configuration2 to 2.2, >> which has made the springframework package imports in MANIFEST.MF >> optional. > > Update: Using this dependency in my bundle project > <dependency> > <groupId>org.apache.commons</groupId> > <artifactId>commons-configuration2</artifactId> > <version>2.2</version> > <scope>compile</scope> > </dependency> > with plain 4.1.1-SNAPSHOT, creates a run-time dependency to version 2.2 > of commons-configuration2 in the feature file, and the need to pull in > springframework non-bundle jars, to make my shiro-core-using bundle load > in karaf, went away. > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
