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).
Right.. looks like my problem is that I've so far used the "-b" (bare) option.
This option behaves differently with 4.0.10 (or say, more correctly). So I'm no
longer using it.
Without this option, however, I need to nudge 'org.apache.karaf.features.cfg'
so the extra test features (all this
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
Ok, interesting. The value of “org.ops4j.pax.url.mvn.repositories” in that
file definitely seems corrupted. It appears that my repeated calls to
“config:property-append” when I start up karaf have been corrupting that. It
didn’t occur to me that the commands entered into the karaf console
Really? I find this somewhat hard to believe, but I'm fairly sure this is the
case.
Anyway. I'm using config admin to update a configuration from within a karaf
command. One of the properties is a string that contains a filename. I'm on
Windows. Filename therefore contains backslashes.
I type
