Actually, your features is causing a refresh (the flairkit-alarm-rest for instance).
So, the features resolver tries to uninstall a bundle to reinstall it. It happens here: https://github.com/apache/karaf/blob/karaf-4.2.x/features/core/src/main/java/org/apache/karaf/features/internal/service/StaticInstallSupport.java#L50 So, your feature will could work at runtime, but with a refresh. I would recommend to fix your bundles to avoid the refresh. Anyway, instead of failing, I can log a WARN message with the bundles in cause. I created KARAF-6370 about that. Regards JB On 26/07/2019 11:40, Matteo Rulli wrote: > Hello, > > Thanks. Yes we use the verify step of the karat-maven-plugin. Does this mean > that the “verify” step can fail at build-time but the feature will work in a > real deployment? If this is the case, what is the right approach to verify a > feature before it is used or deployed? > > Thanks, > Matteo > >> On 26 Jul 2019, at 11:31, Jean-Baptiste Onofré <[email protected]> wrote: >> >> Hi, >> >> I guess you have this with karaf-maven-plugin, right ? >> >> The reason is that we use a "simplified" resolver in the plugin, not >> implementing all methods. That's why you have UnsupportedOperationException. >> >> Regards >> JB >> >> On 26/07/2019 11:05, Matteo Rulli wrote: >>> Hello, >>> >>> Karaf feature resolution fails due to >>> java.lang.UnsupportedOperationException. It is hard to understand the >>> root cause. >>> >>> I managed to reproduce the issue in a relatively simple settings, you >>> can find it here: https://github.com/mrulli/karaf-426-feature-unsupported-op >>> >>> Could you please help me to understand what is it happening here? >>> >>> Thanks, >>> Matteo >> >> -- >> Jean-Baptiste Onofré >> [email protected] >> http://blog.nanthrax.net >> Talend - http://www.talend.com > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
