I think you're right, features-core should be eager by default. or at least the service itself should be eager. I'll fix that asap.
On Mon, Feb 14, 2011 at 11:35, Uwe K. <kort...@t-online.de> wrote: > > Hi, > > in the trunk and karaf-2.2.x-versions actually the boot-features aren't > loaded on startup. > You have to connect to the console and issue at least a "feature:list" > command to get them installed. > > As I see, the default-activation was changed to "lazy" for the > features/core-bundle (with KARAF-443) . > > Am I missing some point, or should this bundle not be loaded in "eager" > mode, to get it started and the boot-features installed? > > Kind regards, > > Uwe Korte. > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Boot-Features-not-started-tp2491610p2491610.html > Sent from the Karaf - Dev mailing list archive at Nabble.com. > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
