Hi All, as a workaround I removed "karaf-framework" from the "featuresBoot" in etc/org.apache.karaf.features.cfg and the container runs nicely with no duplicate logging provider.
Still curios why "karaf-framework" replicates the entries from etc/startup.properties ?! Best Regards, Michael 2014-11-21 14:50 GMT+01:00 Michael Täschner <[email protected]>: > Hi All, > > after getting pax-logging-logback implementation running in ServiceMix > 5.1.x, based on Karaf 2.3.x, I face issues again in ServiceMix 5.3.0 using > Karaf 2.4.0 > > I replaced the pax-logging-service bundle inside etc/startup.properties > (as before) but was surprised to see a pax-logging-service bundle running > in the container. Sifting through features.xml to find the root issue > importing pax-logging-service I found: > > karaf-standard-features: karaf-framework feature declares bundle > pax-logging-service !! I am puzzled: why are these "core" bundles declared > in a feature if they are explicitly started before the feature deployment > through startup.properties ?? Is this duplicate declaration really helpful > ? > > How can I proceed to continue using pax-logging-logback with minimal > changes to the karaf configuration? I already customize startup.properties > as stated before but I am hesitant to override the karaf standard features > xml. > > On a related note: it would be extremely helpful if we had some kind of > reverse search for features, i.e. search feature by bundle (name/symbolic > name) to find where it is declared. > > Thanks and Best Regards, > Michael >
