Thanks for the update Christian,
I do the enhancements (as I did on bundle).
Regards
JB
On 01/04/2012 11:20 PM, Christian Müller wrote:
+1 on this.
It's not possible with Karaf 2.2.5
Christian-Muellers-MacBook-Pro:bin cmueller$ ./karaf clean
__ __
/ //_
+1 on this.
It's not possible with Karaf 2.2.5
Christian-Muellers-MacBook-Pro:bin cmueller$ ./karaf clean
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (2.2
AFAIR, it's already possible (I did an enhancement like this, I'm quite
sure on the bundle, on features, I think so).
Let me check.
Regards
JB
On 01/02/2012 02:41 PM, Guillaume Nodet wrote:
Maybe we should be able to install those in karaf using:
> features:install camel-*
That may solve
Maybe we should be able to install those in karaf using:
> features:install camel-*
That may solve this problem in a different way.
On Sun, Jan 1, 2012 at 15:17, Christian Müller
wrote:
> It looks like it was not one of my best ideas... ;-)
>
> My goal was to have one command to install all Ca
We have the camel-itest-karaf in the test module which will try to
install the karaf feature within PAX-EXAM as Claus has said.
But it need to be ran manually from test/camel-itest-karaf.
On Sun Jan 1 22:17:43 2012, Christian Müller wrote:
It looks like it was not one of my best ideas... ;-)
It looks like it was not one of my best ideas... ;-)
My goal was to have one command to install all Camel features and see
whether or not we can successfully deploy all of them into Karaf.
I agree the better solution is to have an OSGI integration test for all our
components. At least we should ha
On Fri, Dec 30, 2011 at 12:25 PM, Christian Schneider
wrote:
> Do we test to install each feature?
>
> I wonder why we did not catch the problem with some modules not loading.
I think the camel-itest-karaf does install some of the jaxb stuff and
whatnot that camel-cxf does.
Or the fact we may hav
Do we test to install each feature?
I wonder why we did not catch the problem with some modules not loading.
Christian
Am 30.12.2011 11:02, schrieb Claus Ibsen:
On Fri, Dec 30, 2011 at 8:24 AM, Christian Schneider
wrote:
Hi Christian,
I don´t think that would help much. Our recent problem
On Fri, Dec 30, 2011 at 8:24 AM, Christian Schneider
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
+1 to do it with a shell script.
On Fri Dec 30 15:31:58 2011, Jean-Baptiste Onofré wrote:
Hi Christian,
I'm not sure it's a good idea (lot of work, sync, etc). I would prefer
documenting how to do that directly in Karaf directly using a shell
script (with features:list |grep -i camel && featu
Hi Christian,
I'm not sure it's a good idea (lot of work, sync, etc). I would prefer
documenting how to do that directly in Karaf directly using a shell
script (with features:list |grep -i camel && features:install {} or so).
Regards
JB
On 12/29/2011 11:25 PM, Christian Müller wrote:
What d
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 ra
I think that'll be a whole lotta work for something you can do in awk or perl
in about 2 seconds….
Just my .2
On Dec 29, 2011, at 3:25 PM, Christian Müller wrote:
> What do you think about a "camel-all" features which installs all available
> Camel features with one command? This make it more e
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
14 matches
Mail list logo
