Hi, Ha ok, understood.
You have three options: 1. you create your own hibernate feature using same definition as hibernate but changing aries-blueprint to gemini 2. the hibernate feature should use dependency=true on aries-blueprint to avoid "strong" dep 3. blacklisting blueprint should work. By the way, gemini is deprecated, I would strongly recommend to use aries-blueprint (it should be transparent for you). Regards JB On 30/01/2020 19:08, Zhendong Chen wrote: > Thanks JB, I switch to use hibernate of Karaf. But we are using > gemini-blueprint, but the new hibernate version stil using > <feature>aries-blueprint</feature>, this is our problem. > > During this configuration, it started, but do you have another way? > <blacklistedFeatures> > <feature>aries-blueprint</feature> > </blacklistedFeatures> > > > > -- > Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html > -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
