Re: Why is org.apache.aries.blueprint.core.compatibility installed for some some features

I will open an issue. I had already implemented the workaround sugested and is working great. My question was more due to curiosity why a feature not using blueprint would trigger the installation of that bundle. Thank you. João Assunção Email: joao.assun...@exploitsys.com Mobile: +351

Re: Why is org.apache.aries.blueprint.core.compatibility installed for some some features

THis looks like a regression caused by KARAF-4932. Could you please raise a JIRA for this issue ? A workaround could be to modify the generation of you custom assembly so that the blueprint compatibility bundle is installed by default. At least, it would avoid the unwanted refresh of all

Re: Why is org.apache.aries.blueprint.core.compatibility installed for some some features

Of course The feature I'm trying to install: karaf@root()> feature:info paybox-io-modbus Feature paybox-io-modbus 0.1.0.SNAPSHOT Description: Modbus I/O implementation Feature has no configuration Feature has no configuration files Feature has no dependencies. Feature contains followed

Re: Why is org.apache.aries.blueprint.core.compatibility installed for some some features

Can you use feature:install --verbose --all-wiring and send us the output ? 2017-11-08 11:03 GMT+01:00 João Assunção : > Hello all, > > In Karaf 4.1.3 when I do a feature:install one of my features > the org.apache.aries.blueprint.core.compatibility bundle gets

Why is org.apache.aries.blueprint.core.compatibility installed for some some features

Hello all, In Karaf 4.1.3 when I do a feature:install one of my features the org.apache.aries.blueprint.core.compatibility bundle gets installed causing a refresh of all bundles and a Karaf shutdown. None of the bundles in the feature uses blueprint and the more exotic thing is that one of the