> If you want, I can help on these issues, just ping me, we can work
together about that (and I think you will be interested by Karaf 5 ;)).
JB - Thanks. I'll do that. Intrigued to hear about Karaf 5.
Lists - I'll report back here in due course for closure!
Best
Alex
On 23/11/2020 13:40
Hi,
FrameworkStartLevel (framework level), and start level adapt (at bundle level)
and DefaultBundleStartLevel are different things.
I think you are referencing the adapt start level (not the framework start
level, that should be pretty low).
For the deploy folder, Felix FileInstall is started
Thanks very much JB.
To answer your question, we use a boot feature. But consumers might
extend with the deploy folder, specifically placing their extension
bundles into the deploy/ folder _before_ the first start of Karaf. It
is the interplay of hot-deploy `fileinstall` (OSGi startlevel)
Hi Alex,
It depends the way you deploy your bundle (especially if you use the deploy
folder).
The start level is respected in etc/startup.properties or in a feature (as the
resolver can evaluate the order).
However, if you drop first a bundle with startLevel 90 and then, later, a
bundle with s
hi Karaf devs-
i have a question about start-level behaviour in karaf/felix. the osgi
spec says that start-levels should increase 1 by 1 during startup [1].
this doesn't seem to be happening in a clean karaf-based environment.
what we observe is that startlevel jumps directly to the `begi
Hi Brooklyn devs,
Regarding the recent addition to allow custom Bundle Resolver OSGi
services [1], we've discovered a bothersome issue with load order at
runtime. It is non-deterministic whether a custom resolver bundle loads
before or after the initial catalog.bom and persisted state. If
