Hi, it's normal as blueprint is now optional in Karaf 4.2.x.
If you want to use blueprint, you have to install aries-blueprint feature, then you will have the deployer (conditional). Regards JB On 14/12/2019 17:15, tvogel wrote: > I'm in the process of upgrading karaf in my application from 4.0.10 to 4.2.7. > I use the hot deployment feature to deploy a blueprint xml file (DBMS > configuration). > > In (at least) 4.2.6 and 4.2.7 the blueprint deployer is not installed by > default. Below are console sessions from each version. > > This is a change from 4.0.10. > > *4.0.10 karaf* > karaf@root()> feature:list | grep -i deploy > deployer | 4.0.10 | x | > Started | standard-4.0.10 | Karaf Deployer > karaf@root()> bundle:list -t 0 | grep -i deploy > 25 | Active | 24 | 4.0.10 | Apache Karaf :: Deployer :: > Blueprint > 26 | Active | 26 | 4.0.10 | Apache Karaf :: Deployer :: > Features > 27 | Active | 24 | 4.0.10 | Apache Karaf :: Deployer :: > Karaf Archive (.kar) > 28 | Active | 24 | 4.0.10 | Apache Karaf :: Deployer :: > Wrap Non OSGi Jar > karaf@root()> > > *4.2.7 karaf* > karaf@root()> feature:list | grep -i deploy > deployer x 4.2.7 x x x Started > x standard-4.2.7 x Karaf Deployer > karaf@root()> bundle:list -t 0 | grep -i deploy > 18 x Active x 26 x 4.2.7 x Apache Karaf :: Deployer :: Features > 19 x Active x 24 x 4.2.7 x Apache Karaf :: Deployer :: Karaf Archive > (.kar) > 20 x Active x 24 x 4.2.7 x Apache Karaf :: Deployer :: Wrap Non OSGi > Jar > karaf@root()> > > > > How can I get the blueprint deployer installed and working in 4.2.7? > > Timothy > > > > -- > 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
