Hi, so to understand clearly: the "karaf-framework" feature is used to assemble karaf using karaf-maven-plugin ? As such it should rather be configured as "installedFeature" instead of "bootFeatures" as the contained bundles will be managed via startup.properties ? If yes, should I raise a bug for Karaf 2.4.0 ?
Secondly: I get the message about contribution :) I suggest raising improvement issue with new goal features:finditem with bundle-id to display list of features where this bundle is configured. Question would be what the best match criteria is: by Bundle-Symbolic name (and version) ? or by location (mvn identifier) ? I see if I can come up with something ... Cheers, Michael 2014-11-21 15:20 GMT+01:00 Achim Nierbeck <[email protected]>: > Well actually it's the other way round. > The never version of Karaf which is build by the karaf-maven-plugin you'll > need a feature to describe the Karaf container, > allas the karaf-framework feature. > > 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. > > > We really, really love contribution :-) > > regards, Achim > > > 2014-11-21 15:05 GMT+01:00 Michael Täschner <[email protected]>: > >> 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 >>> >> >> > > > -- > > Apache Member > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & > Project Lead > blog <http://notizblog.nierbeck.de/> > Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> > > Software Architect / Project Manager / Scrum Master > >
