If you use fabric then you just specify all the bundles in the same profile. And then fabric installs all those bundles when you assign this profile to containers.
1 of 1 people found this helpful
Thanks for you reply Claus Ibsen.
We are trying to setup a new fuse environment to our client and we want to deploy something like an asset which will take care of a whole bunch of jars.
Currently what we are doing is,
installing a feature repo using : fabric:profile --edit --repositories file:/E:features.xml testProfile
and the feature using: --edit --features someBundle testProfile
Our features.xml is below.
<?xml version="1.0" encoding="UTF-8"?>
<features xmlns="http://karaf.apache.org/xmlns/features/v1.0.0" name="MyFeaturesRepo">
<feature name="example-bundle" resolver="(obr)">
But, we do not see the bundle in the OSGI bundle's list management console.
Is this an expected behaviour??
Because the bundle functionality works fine just that it is not displayed on the OSGI bundles list?
Also is there any better approach that you could suggest us?
I have been asking for this feature for about a year. My understanding is that it will not be implemented - the current focus is to deliver fabric8 v2.