I'm using Karaf 4.0.8
Investigating the karaf-maven-plugin i found the following tag:
For testing purposes, i created a bundle foo.bar and blacklisted it
org.foo.bar/*
it generated a blacklist.properties with:
#
# Generated by the karaf assembly builder
#
# Bundles
ECF provides a full spec-compliant and ct-tested implementation of R6
OSGi Remote Services and Remote Service Admin [1].
As of today's release, ECF's RSA implementation and dependencies are
available via Maven Central [2]. Consequently, the Karaf features
listed at [1] now use Maven
I'm also using Apache Shiro in production, an yes, there is a problem with
the shiro-feature, there is a open pull request to fix that.
https://github.com/apache/shiro/pull/43
--
View this message in context:
http://karaf.922171.n3.nabble.com/Karaf-4-x-Shiro-Support-tp4050311p4050314.html
Hi Stephen,
I’m using Shiro 1.2.4 on Karaf 4.0.7 in production, and tested on 4.0.8.
I just checked, and I’m not using the Shiro feature, instead Shiro Web and Core
jars (and any dependencies) are supplied by Karaf’s maven plugin’s feature
generation. Perhaps I had difficulty with the feature
Hello,
I'm looking at using Apache Shiro for an OSGI project, deployed on Karaf
4.0.8.
I tried to install the shiro feature file: feature:repo-add
mvn:org.apache.shiro/shiro-features/1.2.1/xml/features and it failed with an
error (see below)
I've not found much in the way of documentation for
