Hi JB,
I have managed to deploy my bundle into Karaf 4.0.8. It was important that I
resolved the first issue regarding jansi as this prevented testing with PAX
Exam.
The second issue regarding missing dependencies is either a Felix issue or the
JVM. I've noted that the oracle JRE in the Raspb
Thnx for the reply... can you also elaborate one the function of blacklisted?
Is the purpose to prevent a specific feature from being installed?
--
View this message in context:
http://karaf.922171.n3.nabble.com/Usages-overrides-properties-and-blacklisted-properties-tp4049895p4049898.html
Sent
Hi,
These files allow you to define from whichh feature a bundle comes from.
overrides.properties contains provided bundle URLs not overrided by feature
installation. For instance:
mvn:foo/bar/1.0
means that bar bundle (startup bundle) is provided and overrides all
bundles/packages that a
Hi Jean-Baptiste,
I see.
We would like to separate karaf config (the one in karaf/etc) from our own
config (stored in a separate folder out of karaf install).
We also would like to continue using "config:*" commands which are very
convinient.
As you can see in the karaf code below, the ConfigRep
Hi,
Our feature basically pulls in external two conflicting transaction
managers. Plowing through the documentation and this forum I couldn't find
any documentation that addresses blacklisting a bundle. A file
blacklisted.properties is mentioned and also overrides.properties that might
be of help.
Hi,
You are right for the cluster groups organization:
1. web cluster group to install the "web" application on node2 and node3. The
web cluster group contains only node2 and node3 (not node1).
2. balancer cluster group contains node1, node2, node3, and you only install the
cellar-http-balancer
Hi Kerry,
Agree with Markus in term of version running on ARM platform.
For this issue, it seems more a Felix issue than a Karaf issue. Did you try with
Equinox instead of Felix framework ?
Regards
JB
On 03/19/2017 10:52 PM, JT wrote:
Hi Markus,
Thanks for the reply. I tried 4.0.8 and that
Hi Christian,
You can always specific another value for karaf.etc variable.
It's also possible that you instanciate ConfigRepository with different
constructor args.
However, for convenience, we can introduce a karaf.cfg.storage variable or so.
The purpose of the ConfigRepository is to be ab
Hi all,
Having a look at the implementation of the karaf config:* commands, I
noticed that pid storage is actually managed by
org.apache.karaf.config.core.ConfigRepository
The ConfigRepositoryImpl is instanciated as follow in karaf:
* ConfigRepository configRepository = new
ConfigRepositoryImpl(
