On Fri, Dec 30, 2011 at 8:24 AM, Christian Schneider <ch...@die-schneider.net> wrote: > Hi Christian, > > I don´t think that would help much. Our recent problem where some > dependencies where missing would > not have shown in a camel-all feature as in sum they were there. For users > it is also not practical as installing > all camel-modules takes long and consumes a lot of memory. > > So I rather propose we write a test that installs each camel feature > separately and checks for problems.
We have this in tests\camel-itest-karaf. Its not a script based approach though as it uses pax-exam to setup a karaf instance and install the camel feature. > We could also install some typical combinations to make sure these work. > > Christian > > Am 29.12.2011 23:25, schrieb Christian Müller: > >> What do you think about a "camel-all" features which installs all >> available >> Camel features with one command? This make it more easy to install all >> Camel features in Karaf/SMX and see if it works. >> >> Best, >> Christian >> > > > -- > > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > Talend Application Integration Division http://www.talend.com > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
