Here's the work around I came up with so far:
We add a new feature called the 'karaf-extender' to the featuresBoot.
When started, the extender will load all of the '*.boot' files found in
'etc/featuresBoot.d/'.
These files are expected to contain lines with feature references like:
foo
Indeed, it's not possible right now using a single kar.
I would do using several kar or directly using features.
Where would you define the list of installed features for a given kar
(as it's specific to a kar) ?
Regards
JB
On 07/11/2018 06:14, Jesse White wrote:
> Agreed, using the MANIFEST
Agreed, using the MANIFEST won't get us much further.
We already have a custom Karaf distribution and are looking to provide
extensions (i.e. plugins) as .kar files which be added to existing installs.
Some of these .kar files will contain many features, and we're looking
for a means to control
Hi,
In that case, kar doesn't support it for now. I can create a Jira and
extend the MANIFEST to have a list of startup feature but I'm afraid we
will end with what we already have with features.
Why not using directly the features XML ?
A KAR is basically a Maven repository packaged as a zip
Thanks for the reply JB.
We'd like to control which features are installed outside of the
features XML.
The reason for this is that there are many features available, but we
want to give the user control on which ones to install. In our case,
there are just too many possible permutations to
All;
We're interested in leveraging .kar files to help package plugins and
extend our platform but we've run into a snag.
If a .kar file contains many features and we want to let the user
control which feature(s) to install, is there a way to have these
features installed automatically on a
Hi JB,
I'd prefer the ability to use SCR and just supply a StringEncryptor service if
I could. I'll use blueprint, tried it actually but didn't get it to work.
Being able to use SCR would probably be optimal though.
I installed the jasypt-encryption feature and tried it with the encrypted pwd
