Log commands

Hi. The command "log:tail" only show the rootLogger messages. Is there any way to show messages of others logs? I tried "log:display ALL" but no output was displayed -- View this message in context: http://karaf.922171.n3.nabble.com/Log-commands-tp4048333.html Sent from the Karaf - User

Re: Feature resolution for service capabilities of services with filters

The bnd plugin from the maven bundle plugin used to do that: https://github.com/apache/felix/blob/trunk/tools/maven-bundle-plugin/src/main/resources/org/apache/felix/bundleplugin/scr.xsl I think it's now disabled by default and the bnd one is used. Maybe an upgrade of the maven bundle plugin

Re: A way to extend/parent "assembly-property-edits.xml"

Basically, a profile is a list of files. Files with a cfg extension are handled in a specific way. They are overlayed, as profiles can have a list of parents to inherit from. The profile.cfg is special and contains some profile attributes, such as the list of parents and a list of features or

Re: Feature resolution for service capabilities of services with filters

What is generating the Require-Capabiility header? The target filter isn’t supposed to be there on either Provide- or Require-Capability since it can generally be overridden by configuration. AFAICT the bnd DS processing doesn’t add the target filter to the Require-Capability header. david

Re: A way to extend/parent "assembly-property-edits.xml"

Ok, sorry. Do you have a suggestion how to edit properties files in a different way? On Wed, Oct 12, 2016 at 5:43 PM, Guillaume Nodet wrote: > I wasn't suggesting to use profiles with property-edits, but rather to use > profiles instead of property-edits. > > 2016-10-12

Re: A way to extend/parent "assembly-property-edits.xml"

Yes, maybe it is time for a patch ;-) On Wed, Oct 12, 2016 at 1:44 PM, Markus Rathgeb wrote: > Hi Jens, > > I run into that "property file edit single location" problem myself > from time to time. > I planed to create a patch for that but haven't found any time for this, >

Supported versions of Maven for karaf-maven-plugin

Hello guys, I would need your help with karaf-maven-plugin, please. I cannot find out the minimal version of Maven which is required to use karaf-maven-plugin:features-generate-descriptor goal (in version 4.0.7). In the Karaf docs, the only mention of Maven version is in the "4.1.4.

Re: A way to extend/parent "assembly-property-edits.xml"

Hi Jens, I run into that "property file edit single location" problem myself from time to time. I planed to create a patch for that but haven't found any time for this, yet. Best regards, Markus

Feature resolution for service capabilities of services with filters

Hello guys, we are migrating from Karaf 4.0.5 to 4.0.7 and facing a small issue with the feature resolution. I know that in Karaf 4.0.6 the enforcement of service capabilities when feature is installed became effective. But in our case we use a filter when consuming the service. In Java

Re: A way to extend/parent "assembly-property-edits.xml"

Have you looked at profiles ? You can extend / combine / override stuff, inherit from multiple parents, etc... The assembly-property-edits is more limited imho. 2016-10-06 15:29 GMT+02:00 Jens Reimann : > Hi, > > I am currently building several Apache Karaf distributions and

Re: A way to extend/parent "assembly-property-edits.xml"

Hi Markus, great to see you! Sorry for the late reply. That works quite well for features. However I am looking for a way to do the same for the property edits. The documentation around that says: --- property-file-edits specifies the location of an XML file that specifies edits to 'etc' files