Service Component Runtime provides much better ergonomics with regard to code layout and lifecycle. Most notably it forces proper service separation and is annotation-driven. Having wiring in code also allows the code to not be tailored to a single framework, either.
There are only a few places in controller, which actually are still using blueprint – and we use those as integration tests, mostly.
Gradually reduce dependencies on our blueprint plugin extension and its overall exposure to downstreams, culminating in its removal.
- blocks
-
ODLPARENT-297 Do not pull in org.apache.aries.blueprint.core.compatibility
-
- Confirmed
-
-
-
- Confirmed
-
- relates to
-
ODLMICRO-23
Blueprint Removal
-
- Open
-