Re: What kind of things would prevent a set of bundles from going Active?

Fwiw, the commands works for me on 4.1.x and 4.2.x *karaf*@root()> bundle:headers > headers.txt *karaf*@root()> exec ls LICENSE NOTICE README RELEASE-NOTES bin data deploy etc headers.txt instances karaf.pid lib lock system 2017-10-06 0:13 GMT+02:00 KARR, DAVID

RE: What kind of things would prevent a set of bundles from going Active?

> -Original Message- > From: KARR, DAVID > Sent: Thursday, October 05, 2017 2:14 PM > To: user@karaf.apache.org > Subject: RE: What kind of things would prevent a set of bundles from > going Active? > > > -Original Message- > > From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net]

RE: What kind of things would prevent a set of bundles from going Active?

> -Original Message- > From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] > Sent: Wednesday, October 04, 2017 9:58 PM > To: user@karaf.apache.org > Subject: Re: What kind of things would prevent a set of bundles from > going Active? > > You can actually check the packages available

Re: What kind of things would prevent a set of bundles from going Active?

You can actually check the packages available with the packages:* commands. bundle:headers also gives you details about the wiring. Regards JB On 10/04/2017 07:54 PM, KARR, DAVID wrote: What’s confusing about this is that those packages appear to be present, but perhaps they’re not being

RE: What kind of things would prevent a set of bundles from going Active?

What’s confusing about this is that those packages appear to be present, but perhaps they’re not being presented properly, and the requested version ranges are strange. I find the quartz artifact in my .m2/repository, version 2.1.5 as specified in our properties files. I also find the

Re: What kind of things would prevent a set of bundles from going Active?

For each bundle that can not be resolved diag shows the dependency tree of the requirement the resolver failed on. Typically you look at the line at the bottom. This is what is really missing. In your case it means: The package org.quartz.impl is missing. The package

Re: What kind of things would prevent a set of bundles from going Active?

You could look into ldap filter syntax for a complete explanation. Roughly speaking, there are simple clauses such as a=b, logical operations & | ! and enough parentheses to make everything unambiguous. david jencks > On Oct 2, 2017, at 4:37 PM, KARR, DAVID wrote: > >>

RE: What kind of things would prevent a set of bundles from going Active?

> -Original Message- > From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] > Sent: Friday, September 29, 2017 10:49 PM > To: user@karaf.apache.org > Subject: Re: What kind of things would prevent a set of bundles from > going Active? > > Hi, > > When a bundle is resolved, it means that

Re: What kind of things would prevent a set of bundles from going Active?

Hi, When a bundle is resolved, it means that the constraints resolution is OK. Basically, Import packages & requirements are satisfied. So, a bundle stays in Installed state if it can go to Resolved due to a unsatisfied resolution constraint (for instance an imported package is not present).

What kind of things would prevent a set of bundles from going Active?

I'm still working with the legacy app using Karaf 3.0.1, which I don't have very good overall documentation for. I've been able to execute my "feature:install" command in the karaf console, which appeared to complete successfully, but at that point it's apparently expected that all of my