Our use of Blueprint and general tie-in with OSGi it implies is causing a number of issues.

Blueprint does not do OSGi service wiring right, anyway, so it makes sense to shift to OSGi Declarative Services as the rest of the platform did (and netconf is blocked on aaa). OSGi DS handles service lifecycle correctly and has only metadata footprint, making it a clearly superior alternative to anything blueprint can offer.

This causes grief to odlmicro as well, as they need to maintain bindings.

Experience has shown that doing OSGi DS + javax.inject is very much inlined, with some differences.

Convert all blueprint contains to use OSGi DS, providing javax.inject where convenient.