Re: Why can I not satisfy "(&(osgi.extender=osgi.component)(version>=1.3.0)(!(version>=2.0.0)))"

Oddly I can no longer reproduce the issue. I thought it might have gone away because I'd added: scr into my feature in the features.xml file. However I take that out again and it still works. Odd. If I encounter it again, I'll reduce to a simple test case. > On 14 June 2017 at 09:45

Re: Karaf maven plugin/wrap/slf4j problem

> I propose to share the code and chat directly (on hangout/skype/private > e-mail). Any help you can give me would be greatly appreciated. I have many issues that I'm trying to resolve, as you can tell.

Re: Karaf maven plugin/wrap/slf4j problem

Hi Tom, I will take a look on your code. You custom distribution needs the log feature providing slf4j packages, else wrap will need the slf4j package. Tom, it's really hard to follow how you define your feature/custom distribution. I propose to share the code and chat directly (on

Re: Karaf Feature vs. OBR

Hi David, I think the reason is more that features in karaf used to work a lot simpler in the start. They were simply a list of bundles to install. Over time features got more and more abilities. So it is less to lock in people and more simply a history matter. Since karaf 4 features use the

Re: Karaf Feature vs. OBR

And anyway, Karaf Features can leverage OBR (directly or via Cave). Karaf can load OBR repos in org.apache.karaf.features.cfg and use it directly. Regards JB On 06/14/2017 06:46 PM, Christian Schneider wrote: Hi David, I think the reason is more that features in karaf used to work a lot

Re: Why can I not satisfy "(&(osgi.extender=osgi.component)(version>=1.3.0)(!(version>=2.0.0)))"

For sure, to validate your feature, it has to define scr as inner or dependency feature. Regards JB On 06/14/2017 02:44 PM, t...@quarendon.net wrote: Oddly I can no longer reproduce the issue. I thought it might have gone away because I'd added: scr into my feature in the features.xml

Re: Karaf Feature vs. OBR

Thank you JB and Christian, I think that about answers my question. Right now I don’t have time to actually invest in doing anything about it, but I was just curious. :-) Cheers, =David > On Jun 15, 2017, at 1:49 AM, Jean-Baptiste Onofré wrote: > > And anyway, Karaf

RE: Karaf Feature vs. OBR

When we say "OBR" are we referring to the OSGi Subsystem spec? Scott -Original Message- From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] Sent: Wednesday, June 14, 2017 11:49 AM To: user@karaf.apache.org Subject: Re: Karaf Feature vs. OBR And anyway, Karaf Features can leverage OBR

Re: Karaf Feature vs. OBR

No, the OSGi Repository spec. Regards JB On 06/14/2017 08:43 PM, Leschke, Scott wrote: When we say "OBR" are we referring to the OSGi Subsystem spec? Scott -Original Message- From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] Sent: Wednesday, June 14, 2017 11:49 AM To:

Re: Karaf Feature vs. OBR

I just did a Google search for apache cave nexus to see if anybody provided a comparison, and this is what I found:

Re: Why can I not satisfy "(&(osgi.extender=osgi.component)(version>=1.3.0)(!(version>=2.0.0)))"

> Can you share your sample project ? I will try to put together a simple standalone test case. In fact I'll do that for something else as well that I can't get past.

Why can I not satisfy "(&(osgi.extender=osgi.component)(version>=1.3.0)(!(version>=2.0.0)))"

I'm trying to build a custom karaf distribution using the maven karaf-assembly packaging type. My latest issue is that the build fails with missing requirement osgi.extender; filter:="(&(osgi.extender=osgi.component)(version>=1.3.0)(!(version>=2.0.0)))" I interpret this as meaning the bundle

Re: Why can I not satisfy "(&(osgi.extender=osgi.component)(version>=1.3.0)(!(version>=2.0.0)))"

Hi Tom, also, how does your bnd "project" look like, my gut feeling tells me right now, it might be because of duplicate bundles installed via std. Karaf and bnd-tools, may this be an issue? regards, Achim 2017-06-14 10:08 GMT+02:00 Jean-Baptiste Onofré : > Hi, > > Can you

Re: Complex config

I found this thread because of a similar need -- I store a configuration in yaml format for a java application that I'm "OSGi-fying". The flat dictionary isn't going to work for me, nor is the `${karaf.etc}/worker-config.yaml` method going to work (it won't monitor the worker-config.yaml for

Re: Does hibernate work in karaf 4.1 (it does in 4.0)?

Hi tom, I know Karaf 4.1.1 and Hibernate works, though I don't have an OSS project at hand to prove it. I might sound a bit grumpy, but my gut feeling tells me the root to your issues are those bndtools generated bundles. I fear sometimes they do provide to much "included" when run in a Karaf

Re: Karaf Feature vs. OBR

So if you consider an OBR as being a collection of resources, each resource having capabilities and requirements, then a feature repository is an OBR repository, it's just the syntax is more concise. If you want to look at what the repository look like, you can launch the following command in

Re: Why can I not satisfy "(&(osgi.extender=osgi.component)(version>=1.3.0)(!(version>=2.0.0)))"

That would be great. In the mean time, I'm testing with the karaf-samples I prepared for the dev guide update. Regards JB On 06/14/2017 10:24 AM, t...@quarendon.net wrote: Can you share your sample project ? I will try to put together a simple standalone test case. In fact I'll do that

Karaf maven plugin/wrap/slf4j problem

I have put together a simple example of the problem I'm been encountering attempting to create a custom karaf distribution. If you attempt to include a bundle such as org.apache.felix:org.apache.felix.http.servlet-api in a feature, you get this build error: missing requirement