Yes, I've tried using staged boot, but in 3.0.x it caused some classpath issues with CXF. It would be great if we could just set up our features so that they're just installed in the order they're defined.
On Fri, Nov 18, 2016 at 10:56 AM Guillaume Nodet <[email protected]> wrote: > You mean installing the features one by one instead of all in one go ? > Have you tried using > (myfeature1,myfeature2),(myfeature3,myfeature4) > so that you end up with 2 stages ? > Ultimately, you can use > (myfeature1),(myfeature2),(myfeature3),(myfeature4) > > 2016-11-18 16:44 GMT+01:00 James Carman <[email protected]>: > > > Karaf 3.0.8+ now provides predictable boot feature startup order, but the > > 4.0.x line does not provide that guarantee. It apparently tries to be > > smart and figure out what you need, but sometimes it just works better if > > we can let the user control things explicitly. Is there, perhaps, a > > compromise here? Could we perhaps have a switch in the > > org.apache.karaf.features.cfg file that allows you to turn on manual > > control of the startup order? I'm not the only one who has encountered > > this issue. There have been emails recently where other folks have > > observed it. Thoughts? > > > > James > > > > > > -- > ------------------------ > Guillaume Nodet > ------------------------ > Red Hat, Open Source Integration > > Email: [email protected] > Web: http://fusesource.com > Blog: http://gnodet.blogspot.com/ >
