You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Christian Müller <ch...@gmail.com> on 2012/01/01 15:17:43 UTC
Re: Whats about a camel-all feature
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 have a (empty) test which use our features
file to deploy the component into Karaf (with the jre.properties.cxf)
configuration. I will have a look into our OSGI integraton tests an see
whether we can improve something here to avoid the issues we had with our
last release candidate. If so, I will raise a JIRA for it...
Best,
Christian
Re: Whats about a camel-all feature
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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
> __ __ ____
> / //_/____ __________ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
>
> Apache Karaf (2.2.5)
>
> Hit '<tab>' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '<ctrl-d>' or 'osgi:shutdown' to shutdown Karaf.
>
> karaf@root> features:addurl
> mvn:org.apache.camel.karaf/apache-camel/2.9.0/xml/features
> karaf@root> features:install camel-*
> Error executing command: No feature named 'camel-*' with version '0.0.0'
> available
>
> Best,
> Christian
>
> On Mon, Jan 2, 2012 at 2:45 PM, Jean-Baptiste Onofré<jb...@nanthrax.net>wrote:
>
>> 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 this problem in a different way.
>>>
>>> On Sun, Jan 1, 2012 at 15:17, Christian Müller
>>> <ch...@gmail.com> wrote:
>>>
>>>> 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 have a (empty) test which use our features
>>>> file to deploy the component into Karaf (with the jre.properties.cxf)
>>>> configuration. I will have a look into our OSGI integraton tests an see
>>>> whether we can improve something here to avoid the issues we had with our
>>>> last release candidate. If so, I will raise a JIRA for it...
>>>>
>>>> Best,
>>>> Christian
>>>>
>>>
>>>
>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Whats about a camel-all feature
Posted by Christian Müller <ch...@gmail.com>.
+1 on this.
It's not possible with Karaf 2.2.5
Christian-Muellers-MacBook-Pro:bin cmueller$ ./karaf clean
__ __ ____
/ //_/____ __________ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (2.2.5)
Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '<ctrl-d>' or 'osgi:shutdown' to shutdown Karaf.
karaf@root> features:addurl
mvn:org.apache.camel.karaf/apache-camel/2.9.0/xml/features
karaf@root> features:install camel-*
Error executing command: No feature named 'camel-*' with version '0.0.0'
available
Best,
Christian
On Mon, Jan 2, 2012 at 2:45 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
> 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 this problem in a different way.
>>
>> On Sun, Jan 1, 2012 at 15:17, Christian Müller
>> <ch...@gmail.com> wrote:
>>
>>> 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 have a (empty) test which use our features
>>> file to deploy the component into Karaf (with the jre.properties.cxf)
>>> configuration. I will have a look into our OSGI integraton tests an see
>>> whether we can improve something here to avoid the issues we had with our
>>> last release candidate. If so, I will raise a JIRA for it...
>>>
>>> Best,
>>> Christian
>>>
>>
>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: Whats about a camel-all feature
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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 this problem in a different way.
>
> On Sun, Jan 1, 2012 at 15:17, Christian Müller
> <ch...@gmail.com> wrote:
>> 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 have a (empty) test which use our features
>> file to deploy the component into Karaf (with the jre.properties.cxf)
>> configuration. I will have a look into our OSGI integraton tests an see
>> whether we can improve something here to avoid the issues we had with our
>> last release candidate. If so, I will raise a JIRA for it...
>>
>> Best,
>> Christian
>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Whats about a camel-all feature
Posted by Guillaume Nodet <gn...@gmail.com>.
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
<ch...@gmail.com> wrote:
> 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 have a (empty) test which use our features
> file to deploy the component into Karaf (with the jre.properties.cxf)
> configuration. I will have a look into our OSGI integraton tests an see
> whether we can improve something here to avoid the issues we had with our
> last release candidate. If so, I will raise a JIRA for it...
>
> Best,
> Christian
--
------------------------
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: Whats about a camel-all feature
Posted by Willem Jiang <wi...@gmail.com>.
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... ;-)
>
> 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 have a (empty) test which use our features
> file to deploy the component into Karaf (with the jre.properties.cxf)
> configuration. I will have a look into our OSGI integraton tests an see
> whether we can improve something here to avoid the issues we had with our
> last release candidate. If so, I will raise a JIRA for it...
>
> Best,
> Christian
>
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang