Re: OSGI dependencies question
Hi Bilgrin
I hope to go out from the hospital tomorrow. I should be able to help you
tomorrow evening.
Regards
JB
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://wwx.talend.com
- Reply message -
From: "Bilgin Ibryam"
To:
Subject: OSGI dependencies question
Date: Mon, Jul 16, 2012 8:27 pm
Hi all,
I am working on CAMEL-4691 a CMIS component but have difficulties adding
the OSGI dependencies. Any help on the following points is greatly
appreciated:
1. Is there any documentation on the format of features.xml
2. How do you figure out if a dependency is available as osgi bundle, or as
ServiceMix bundle...
3. The blocker: opencmis is already OSGI bundled
http://chemistry.apache.org/java/developing/dev-osgi.html so I added the
following lines in features.xml (I am not sure if it is correct)
camel-core
mvn:org.apache.chemistry.opencmis/chemistry-opencmis-osgi-server/${cmis-bundle-version}
mvn:org.apache.camel/camel-cmis/${project.version}
But when I try to validate the features, I get the following error:
[WARNING] Failed to validate feature camel-cmis
[WARNING] No export found to match
org.apache.chemistry.opencmis.client.runtime (imported by
mvn:org.apache.camel/camel-cmis/2.11-SNAPSHOT)
[WARNING] No export found to match javax.xml.ws.soap (imported by
mvn:org.apache.chemistry.opencmis/chemistry-opencmis-osgi-server/0.5.0)
[WARNING] No export found to match javax.xml.ws (imported by
mvn:org.apache.chemistry.opencmis/chemistry-opencmis-osgi-server/0.5.0)
[WARNING] No export found to match javax.xml.ws.handler (imported by
mvn:org.apache.chemistry.opencmis/chemistry-opencmis-osgi-server/0.5.0)
[WARNING] No export found to match
org.apache.chemistry.opencmis.client.api;version="[0.5,1)" (imported by
mvn:org.apache.camel/camel-cmis/2.11-SNAPSHOT)
[WARNING] No export found to match javax.jws (imported by
mvn:org.apache.chemistry.opencmis/chemistry-opencmis-osgi-server/0.5.0)
How to find out if these dependencies are available?
Thanks
Bilgin
Re: svn commit: r1408670 - in /camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf: ./ mtom/
Hi guys, I have access to my AIX box from here. I will update my local working copy to run the tests tonight (east coast time). Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Daniel Kulp" To: , "Claus Ibsen" Subject: svn commit: r1408670 - in /camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf: ./ mtom/ Date: Wed, Nov 14, 2012 7:42 am On Nov 14, 2012, at 2:07 AM, Claus Ibsen wrote: > On Tue, Nov 13, 2012 at 1:25 PM, Daniel Kulp wrote: >> >> >> Can I ask why they cannot run on AIX? Other than the images which may not >> work headless, the tests should be able to run fine.I've afraid this is >> addressing a symptom, not the actual problem and I prefer to get the problem >> looked at. >> > > Yeah there was nothing obvious I could see from the junit error that > indicated why it didn't work on AIX. > I needed to disable failing tests to have the build and tests be able > to do a full test suite of the project to also uncover issues further > down the road.' If that's the case, I'm -1 on all the "disable on AIX" commits you did. Disabling a test just because you don't know why its failing is not OK. There aren't even descriptions of what's failing, stack traces, whatever, that would allow others on the list help diagnose it. I'm also concerned because we did have these running OK on AIX not too long ago. Thus it may be something with your specific AIX instance. When JB gets back to France, I'll see if we can retry on his AIX box. > Though its suspicious that these tests are using images and detect for > headless mode. Wonder if we can use non images for the test? Well, it's specifically there to test the images. JAX-WS requires mapping certain wsdl constructs to Images as part of the wsdl2java process (although it's a relatively annoying part of the spec, I'd personally prefer DataSource or similar). The test is there to specifically test that part of the spec. Unfortunately, it won't work with headless. (actually, that may need to be re-checked. That was true with Java5, not sure with 6 or 7. I'll double check that today as that could allow re-enabling some test in CXF on trunk that no longer supports 5) Dan > >> Dan >> >> >> >> On Nov 13, 2012, at 5:35 AM, davscl...@apache.org wrote: >> >>> Author: davsclaus >>> Date: Tue Nov 13 10:35:20 2012 >>> New Revision: 1408670 >>> >>> URL: http://svn.apache.org/viewvc?rev=1408670&view=rev >>> Log: >>> Skip test that cannot run on aix >>> >>> Added: >>> >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/TestHelper.java >>>(with props) >>> Modified: >>> >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/mtom/CxfJavaMtomProducerPayloadTest.java >>> >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/mtom/CxfMtomConsumerPayloadModeTest.java >>> >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/mtom/CxfMtomConsumerTest.java >>> >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/mtom/CxfMtomDisabledProducerPayloadModeTest.java >>> >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/mtom/CxfMtomPOJOProducerTest.java >>> >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/mtom/CxfMtomProducerPayloadModeTest.java >>> >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/mtom/CxfMtomRouterPayloadModeTest.java >>> >>> Added: >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/TestHelper.java >>> URL: >>> http://svn.apache.org/viewvc/camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/TestHelper.java?rev=1408670&view=auto >>> == >>> --- >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/TestHelper.java >>> (added) >>> +++ >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/TestHelper.java >>> Tue Nov 13 10:35:20 2012 >>> @@ -0,0 +1,41 @@ >>> +/** >>> + * Licensed to the Apache Software Foundation (ASF) under one or more >>> + * contributor license agreements. See the NOTICE file distributed with >>> + * this work for additional information regarding copyright ownership. >>> + * The ASF licenses this file to You under the Apache License, Version 2.0 >>> + * (the "License"); you may not use this file except in compliance with >>> + * the License. You may obtain a copy of the License at >>> + * >>> + * http://www.apache.org/licenses/LICENSE-2.0 >>> + * >>> + * Unless required by applicable law or agreed to in writing, software >>> + * distributed under the License is distributed on an "AS IS" BASIS, >>> + * WITHOUT WARRAN
Re: svn commit: r1408670 - in /camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf: ./ mtom/
Hi guys, I have access to my AIX box from here. I will update my local working copy to run the tests tonight (east coast time). Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Daniel Kulp" To: , "Claus Ibsen" Subject: svn commit: r1408670 - in /camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf: ./ mtom/ Date: Wed, Nov 14, 2012 7:42 am On Nov 14, 2012, at 2:07 AM, Claus Ibsen wrote: > On Tue, Nov 13, 2012 at 1:25 PM, Daniel Kulp wrote: >> >> >> Can I ask why they cannot run on AIX? Other than the images which may not >> work headless, the tests should be able to run fine.I've afraid this is >> addressing a symptom, not the actual problem and I prefer to get the problem >> looked at. >> > > Yeah there was nothing obvious I could see from the junit error that > indicated why it didn't work on AIX. > I needed to disable failing tests to have the build and tests be able > to do a full test suite of the project to also uncover issues further > down the road.' If that's the case, I'm -1 on all the "disable on AIX" commits you did. Disabling a test just because you don't know why its failing is not OK. There aren't even descriptions of what's failing, stack traces, whatever, that would allow others on the list help diagnose it. I'm also concerned because we did have these running OK on AIX not too long ago. Thus it may be something with your specific AIX instance. When JB gets back to France, I'll see if we can retry on his AIX box. > Though its suspicious that these tests are using images and detect for > headless mode. Wonder if we can use non images for the test? Well, it's specifically there to test the images. JAX-WS requires mapping certain wsdl constructs to Images as part of the wsdl2java process (although it's a relatively annoying part of the spec, I'd personally prefer DataSource or similar). The test is there to specifically test that part of the spec. Unfortunately, it won't work with headless. (actually, that may need to be re-checked. That was true with Java5, not sure with 6 or 7. I'll double check that today as that could allow re-enabling some test in CXF on trunk that no longer supports 5) Dan > >> Dan >> >> >> >> On Nov 13, 2012, at 5:35 AM, davscl...@apache.org wrote: >> >>> Author: davsclaus >>> Date: Tue Nov 13 10:35:20 2012 >>> New Revision: 1408670 >>> >>> URL: http://svn.apache.org/viewvc?rev=1408670&view=rev >>> Log: >>> Skip test that cannot run on aix >>> >>> Added: >>> >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/TestHelper.java >>>(with props) >>> Modified: >>> >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/mtom/CxfJavaMtomProducerPayloadTest.java >>> >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/mtom/CxfMtomConsumerPayloadModeTest.java >>> >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/mtom/CxfMtomConsumerTest.java >>> >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/mtom/CxfMtomDisabledProducerPayloadModeTest.java >>> >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/mtom/CxfMtomPOJOProducerTest.java >>> >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/mtom/CxfMtomProducerPayloadModeTest.java >>> >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/mtom/CxfMtomRouterPayloadModeTest.java >>> >>> Added: >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/TestHelper.java >>> URL: >>> http://svn.apache.org/viewvc/camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/TestHelper.java?rev=1408670&view=auto >>> == >>> --- >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/TestHelper.java >>> (added) >>> +++ >>> camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/TestHelper.java >>> Tue Nov 13 10:35:20 2012 >>> @@ -0,0 +1,41 @@ >>> +/** >>> + * Licensed to the Apache Software Foundation (ASF) under one or more >>> + * contributor license agreements. See the NOTICE file distributed with >>> + * this work for additional information regarding copyright ownership. >>> + * The ASF licenses this file to You under the Apache License, Version 2.0 >>> + * (the "License"); you may not use this file except in compliance with >>> + * the License. You may obtain a copy of the License at >>> + * >>> + * http://www.apache.org/licenses/LICENSE-2.0 >>> + * >>> + * Unless required by applicable law or agreed to in writing, software >>> + * distributed under the License is distributed on an "AS IS" BASIS, >>> + * WITHOUT WARRAN
Re: [VOTE] Release Apache Camel 2.12.0 (RC2)
Hi Christian,
It's due to xerces in lib/endorsed (required to fix an issue with IBM jdk), and
a forget of the systemPackages property.
I already created the jira and I will fix that for Karaf 2.3.3.
The workaround is to remove xerces jar from lib/endorsed.
Regards
JB
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://wwx.talend.com
- Reply message -
From: "Christian Schneider"
To:
Subject: [VOTE] Release Apache Camel 2.12.0 (RC2)
Date: Sun, Sep 8, 2013 9:25 am
+1
I tested some tutorial examples in Apache Karaf 2.3.2 and Apache Karaf
2.3.1.
I had one problem though. When testing the example
https://github.com/cschneider/Karaf-Tutorial/tree/master/camel/order I
got the error below.
I also tested on camel 2.11.1 and got the same error. So this is no new
regression. I tested camel 2.12.0 on karaf 2.3.1 now too and there it
worked. So this may be a problem in karaf 2.3.2.
I will look into the error in more detail and open an issue if the
problem is in camel.
Christian
2013-09-08 09:10:51,956 | WARN | file://ordersin |
GenericFileOnCompletion | ent.file.GenericFileOnCompletion 161
| 60 - org.apache.camel.camel-core - 2.12.0 | Rollback file strategy:
org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy@1f7e9bc
for file: GenericFile[order1.xml]
2013-09-08 09:10:52,580 | ERROR | file://ordersin |
DefaultErrorHandler | rg.apache.camel.util.CamelLogger 215
| 60 - org.apache.camel.camel-core - 2.12.0 | Failed delivery for
(MessageId: ID-wschris-63101-1378624109305-0-257 on ExchangeId:
ID-wschris-63101-1378624109305-0-258). Exhausted after delivery attempt:
1 caught: org.apache.camel.TypeConversionException: Error during type
conversion from type: java.io.BufferedInputStream to the required type:
org.w3c.dom.Document with value java.io.BufferedInputStream@3f721f due
javax.xml.parsers.FactoryConfigurationError: Provider
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found
Message History
---
RouteId ProcessorId Processor Elapsed (ms)
[order ] [order ] [file://ordersin?noop=true ]
[ 110]
[order ] [setHeader1] [setHeader[customer] ] [
110]
Exchange
---
Exchange[
Id ID-wschris-63101-1378624109305-0-258
ExchangePattern InOnly
Headers {breadcrumbId=ID-wschris-63101-1378624109305-0-257,
CamelFileAbsolute=false,
CamelFileAbsolutePath=D:\java\apache-karaf-2.3.2\ordersin\order1.xml,
CamelFileLastModified=1335128170616, CamelFileLength=221,
CamelFileName=order1.xml, CamelFileNameOnly=order1.xml,
CamelFileParent=ordersin, CamelFilePath=ordersin\order1.xml,
CamelFileRelativePath=order1.xml, CamelRedelivered=false,
CamelRedeliveryCounter=0}
BodyType org.apache.camel.component.file.GenericFile
Body[Body is file based: GenericFile[order1.xml]]
]
Stacktrace
---
org.apache.camel.TypeConversionException: Error during type conversion
from type: java.io.BufferedInputStream to the required type:
org.w3c.dom.Document with value java.io.BufferedInputStream@3f721f due
javax.xml.parsers.FactoryConfigurationError: Provider
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found
at
org.apache.camel.impl.converter.BaseTypeConverterRegistry.convertTo(BaseTypeConverterRegistry.java:130)[60:org.apache.camel.camel-core:2.12.0]
at
org.apache.camel.core.osgi.OsgiTypeConverter.convertTo(OsgiTypeConverter.java:107)[62:org.apache.camel.camel-blueprint:2.12.0]
at
org.apache.camel.builder.xml.XPathBuilder.doGetDocument(XPathBuilder.java:1113)[60:org.apache.camel.camel-core:2.12.0]
at
org.apache.camel.builder.xml.XPathBuilder.getDocument(XPathBuilder.java:1092)[60:org.apache.camel.camel-core:2.12.0]
at
org.apache.camel.builder.xml.XPathBuilder.doInEvaluateAs(XPathBuilder.java:881)[60:org.apache.camel.camel-core:2.12.0]
at
org.apache.camel.builder.xml.XPathBuilder.evaluateAs(XPathBuilder.java:778)[60:org.apache.camel.camel-core:2.12.0]
at
org.apache.camel.builder.xml.XPathBuilder.evaluate(XPathBuilder.java:748)[60:org.apache.camel.camel-core:2.12.0]
at
org.apache.camel.builder.xml.XPathBuilder.evaluate(XPathBuilder.java:168)[60:org.apache.camel.camel-core:2.12.0]
at
org.apache.camel.builder.ProcessorBuilder$4.process(ProcessorBuilder.java:103)[60:org.apache.camel.camel-core:2.12.0]
at
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[60:org.apache.camel.ca
Re: [VOTE] Release Apache Camel 2.10.7
+1 (non binding) Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Jon Anstey" To: Subject: [VOTE] Release Apache Camel 2.10.7 Date: Mon, Sep 16, 2013 2:32 pm +1 On 2013-09-15 5:26 PM, "Christian Müller" wrote: > After 2 month of development, we have a new bug fix release candidate > apache-camel-2.10.7 ready. > It comes with 63 issues resolved: new features, improvements and bug fixes > [1]. > You can find the release notes here [2]. > This will be the last planned Camel 2.10.x release. We will discontinue the > support for the camel-2.10.x branch afterwards. > > Please find the staging repo here: > https://repository.apache.org/content/repositories/orgapachecamel-048/ > > The tarballs are here > > https://repository.apache.org/content/repositories/orgapachecamel-048/org/apache/camel/apache-camel/2.10.7/ > > Tag: > > https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=5d46d83f26fec7c06a9e531aee45e1048fed84af > > Please review, help out with testing and vote to approve this release > binary. Please mention what you tested to prevent duplicate work. Your vote > counts! > > [ ] +1 Release the binary as Apache Camel 2.10.7 > [ ] -1 Veto the release (provide specific comments) > Vote is open for at least 72 hours. > > Thanks in advance, > Christian > > [1] > > https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%20%222.10.7%22%20AND%20project%20%3D%20CAMEL > [2] > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12324667 >
Re: [VOTE] Release Apache Camel 2.13.0
+1 (non binding) Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Grzegorz Grzybek" To: Subject: [VOTE] Release Apache Camel 2.13.0 Date: Thu, Mar 20, 2014 8:31 am +1 (non binding) I've successfully built camel 2.13.0 using Maven 3.2.1. It however failed using shiny new JDK1.8.0_00 with the following exception: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.6:run (generate-sources) on project camel-spring: An Ant BuildException has occured: taskdef A class needed by class com.sun.tools.jxc.SchemaGenTask cannot be found: com/sun/mirror/apt/AnnotationProcessorFactory regards Grzegorz Grzybek 2014-03-20 7:53 GMT+01:00 Claus Ibsen : > Hi > > I noticed 2 missing components in lib dir > - camel-ical > - camel-infinispan > > And the manual has (c) 2013 > > > I gave a couple of examples a test spin. And so far looks good. > > +1 > > > On Tue, Mar 18, 2014 at 6:19 AM, Willem Jiang > wrote: > > This is a vote to release Apache Camel 2.13.0, a major release coming > > with about 480 issues fixed. > > > > Release notes: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324786&styleName=&projectId=12311211 > > > > Staging repo: > > https://repository.apache.org/content/repositories/orgapachecamel-1005 > > > > Tarballs: > > > https://repository.apache.org/content/repositories/orgapachecamel-1005/org/apache/camel/apache-camel/2.13.0/ > > > > Tag: > > > https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ab6c7538b31407094692c7083077b8a3c490bda8 > > > > Please test this release candidate and cast your vote. > > [ ] +1 Release the binary as Apache Camel 2.13.0 > > [ ] -1 Veto the release (provide specific comments) > > Vote is open for at least 72 hours. > > > > -- > > Willem Jiang > > > > Red Hat, Inc. > > Web: http://www.redhat.com > > Blog: http://willemjiang.blogspot.com (English) > > http://jnn.iteye.com (Chinese) > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > > > > > > > -- > Claus Ibsen > - > Red Hat, Inc. > Email: cib...@redhat.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > Make your Camel applications look hawt, try: http://hawt.io >
Re: Wiki edit rights
Hi Antoine, I'm pretty sure we gonna give it to you asap. Unfortunately I can't right now, I'm with a customer. Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Antoine DESSAIGNE" To: "Camel Development" Subject: Wiki edit rights Date: Thu, Jun 5, 2014 8:23 am Hi everyone, I've signed the ICLA, could someone grant me the wiki edit rights so I can update the documentation according to my pull requests ? My JIRA username is antoine.dessaigne Thanks a lot, Antoine.
Re: Wiki edit rights
Hi Claus, By "we", I meant "apache guys" including infra ;) We have to open the jira to the infra, that's why it's asap (actually it's when the infra will have time ;)). Thanks ! Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Claus Ibsen" To: "dev" Subject: Wiki edit rights Date: Thu, Jun 5, 2014 8:32 am On Thu, Jun 5, 2014 at 8:29 AM, j...@nanthrax.net wrote: > Hi Antoine, > > I'm pretty sure we gonna give it to you asap. Unfortunately I can't right > now, I'm with a customer. > No its not possible anymore. As INFRA change the permissions. We are in talks with them to make it back like old days where we could handle this ourselves, instead of having to bother INFRA every time, and wait days/weeks for them to react. > Regards > JB > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://wwx.talend.com > > - Reply message - > From: "Antoine DESSAIGNE" > To: "Camel Development" > Subject: Wiki edit rights > Date: Thu, Jun 5, 2014 8:23 am > > > Hi everyone, > > I've signed the ICLA, could someone grant me the wiki edit rights so I can > update the documentation according to my pull requests ? > > My JIRA username is antoine.dessaigne > > Thanks a lot, > > Antoine. -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Re: Camel 2.8.0 in fuse service mix
Hi ServiceMix 4.4 will use Camel 2.8.0 or 2.8.1. Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "skompelly" To: Subject: Camel 2.8.0 in fuse service mix Date: Thu, Aug 25, 2011 5:03 pm Hi As i know recently Camel 2.8.0 has been released. I am in need of using Fuse Service Mix with camel 2.8.0 version. I dont want to install the 2.8.0 bundles on top of existing service mix. Which release/version of service mix does it support camel 2.8.0 version? When that service mix release will happen? Thanks in Advance, Regards, Santosh -- View this message in context: http://camel.465427.n5.nabble.com/Camel-2-8-0-in-fuse-service-mix-tp4734805p4734805.html Sent from the Camel Development mailing list archive at Nabble.com.
Re: [DISCUSS] fifth Camel sub-forum camel-issues
+1 Good idea. Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Christian Müller" To: Subject: [DISCUSS] fifth Camel sub-forum camel-issues Date: Thu, Oct 27, 2011 12:03 am At present, we have four sub-forums: - camel-users - camel-commits - camel-development - camel-extra What's about adding a fifth sub-forum "camel-issues" (as we already have for CXF) and send all [jira] messages into this forum? I could imagine we have to much messages in the camel-development forum which are not really interesting for the developers subscribed to this list. Maybe this is the reason why some discussions are not very active. Maybe we overlooked they... Best, Christian
Re: [DISCUSS] - Align Camel karaf commands as Karaf is doing
Hi Christian, I would wait the subshells and let the commands as it is. My 2 cents ;) Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Christian Schneider" To: Subject: [DISCUSS] - Align Camel karaf commands as Karaf is doing Date: Thu, Dec 8, 2011 12:05 pm The number of characters per command is the same. Using tab can save you from typing most characters in both styles. So I think the focus on resources really makes the difference and I think it is more natural to think in resources for humans than in commands. Christian Am 08.12.2011 10:38, schrieb Charles Moulliard: > Hi, > > I prefer that we keep as command family name a short name. "camel" is > fine but "camel-route" or "camel-context" are too long. Imagine when > operating a project on a platform, the number of characters to be > typed on the keyboard. This has an impact which is not negligible. > > So why not using camel:lisr-routes, camel:list-contexts and their > shortcut clr, clc > > Regards, > > Charles > > > On 08/12/11 09:49, Christian Schneider wrote: >> >> I really like the idea of having camel:route and then simply call >> list or start or stop. >> >> We can even do that without the sub shells already by naming the >> commands slightly different. >> >> Instead >> camel:route-list >> camel:context-list >> >> I propose to have: >> camel-route:list >> camel-context:list >> >> This would be more similar to the later sub shell commands. >> >> Christian >> >> >> Am 05.12.2011 09:54, schrieb James Strachan: >>> On 2 December 2011 15:29, Claus Ibsen wrote: Hi On the Karaf @dev they are talking about changing the naming of the commands. http://karaf.922171.n3.nabble.com/PROPOSAL-New-Karaf-commands-norm-td3430815.html eg camel:list-routes --> camel:route-list >>> Or we could even go with route:list so when there's sub shells we >>> could do >>> >>> shell camel:route >>> list >>> start foo >>> stop bar >>> >>> etc >>> >> >> -- Christian Schneider http://www.liquid-reality.de Open Source Architect Talend Application Integration Division http://www.talend.com
Re: [VOTE] Release Apache Camel 2.9.0
Good idea ;) Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Daniel Kulp" To: Subject: [VOTE] Release Apache Camel 2.9.0 Date: Tue, Dec 20, 2011 3:51 pm Just an FYI: I've asked Olivier Lamy to look into getting maven to fail the build if the tag exists. (It's good to be the boss ;-)It's now logged as: http://jira.codehaus.org/browse/MRELEASE-722 so some future version of the release plugin won't let this happen. I've seen this happen way too many times now.Needs to get fixed. Dan On Monday, December 19, 2011 11:27:39 PM Daniel Kulp wrote: > I think there is something wrong with the tag. > > > I see a "trunk" dir in: > > http://svn.apache.org/repos/asf/camel/tags/camel-2.9.0/ > > which looks like it has all of camel in it as well. I think the tag is > wrong (likely didn't delete the old tag?) and I'm not really sure which was > built for the release. > > Dan > > On Monday, December 19, 2011 11:20:35 PM Hadrian Zbarcea wrote: > > A new release candidate apache-camel-2.9.0 final is out with > > approximately 478 issues resolved so far: improvements and bug fixes > > [1]. > > > > Please find the staging repo here: > > https://repository.apache.org/content/repositories/orgapachecamel-374/ > > > > The tarballs are here > > https://repository.apache.org/content/repositories/orgapachecamel-374/or > > g/ap ache/camel/apache-camel/2.9.0/ > > > > Tag: > > http://svn.apache.org/repos/asf/camel/tags/camel-2.9.0/ > > > > Please review, help out with testing and vote to approve this release > > binary. Your vote counts! > > > > [ ] +1 Release the binary as Apache Camel 2.9.0 > > [ ] -1 Veto the release (provide specific comments) > > Vote is open for at least 72 hours. > > > > I still need to finish checking all the artifacts. I will do it and cast > > my vote in the morning. > > Hadrian > > > > [1] > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1231121 > > 1&ve rsion=12316374 -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
Re: [DISCUSS] Dropping support for Camel 2.7.x
+1 -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Christian Müller" To: "dev@camel.apache.org" Subject: [DISCUSS] Dropping support for Camel 2.7.x Date: Sat, Dec 31, 2011 7:43 pm When we release Camel 2.9.0 (expected in the next days) and start working on Camel 2.10, I would like to cut a new release from the camel-2.7.x branch which will be in my opinion the last Camel 2.7 release because we discussed to support the two privios relases which then are Camel 2.8 and 2.9. What do you think? Happy new year! Christian Sent from a mobile device
