Re: FeaturesService deploying old bundle versions

2016-07-25 Thread jkreutzfeld
Sure, here are the manifests (i removed imports and exports for readability). They are built by maven, so they are basically the same. Version 1.0.9: Manifest-Version: 1.0 Build-Timestamp: 20160513-1319 Bundle-ClassPath: . Tool: Bnd-1.50.0 Bundle-Name: Components :: UserRelations ::

FeaturesService deploying old bundle versions

2016-07-25 Thread jkreutzfeld
Hello everyone, in our application we built a plugin service using the karaf FeaturesService. Our plugins are zip files containing the bundles to deploy and the feature.xml, which looks like this: http://karaf.apache.org/xmlns/features/v1.2.0;

Karaf 4.0.5: Failed to install wrapped bundle from feature.xml

2016-07-25 Thread martina.rapp
Hello everybody, we need to upgrade from Karaf 2.x to Karaf 4.x. Therefore I'm currenlty testing the latest Karaf version on Windows7 with a very simple example. I just want to install a wrapped 3rd-party jar as a feature to my plain Karaf installation. I'm using the following feature.xml file:

Karaf doesn't use proper Time Zone

2016-07-25 Thread Andrei Petru Mura
Hi everybody, I'm using Apache Karaf 4.0.4. I recently upgraded to it. All works perfect, except the fact that time has disabled the daylight savings. So, for example if I use CEST time, it actually uses CET time, if I use EEST time, it actually uses EET time. Can anybody give me any hints about

Re: Connect pax-logging/Log4j with 3rd party Jar

2016-07-25 Thread Althaus, Volker
Hi Guillaume, Thanks for reply. Unfortunately this is exactly the bundle setup I've used so far. I am not happy with that because I have to maintain two log4j configurations, therefore I am searching for a solution to integrate pax-logging somehow. Regards Von: Guillaume Nodet

Re: Connect pax-logging/Log4j with 3rd party Jar

2016-07-25 Thread Guillaume Nodet
In such a case, one possibility would be to create an uber bundle containing the library + an embedded version of log4j, without importing the package. It will force that library to use the embedded version of log4j which will be complete. So you won't run into ClassNotFoundException, but the