IRC channels - Codehaus to Freenode

Hi folks. Codehaus is shuttering its doors and as of May 17th, 2015 and all accounts and services will be terminated. All IRC channel traffic should be migrated over to freenode (chat.freenode.net ) to the following channels: #apache-cxf #apache-camel #apache-activem

Re: [PROPOSAL] Move IRC channel to freenode ?

+1… this probably needs to happen pretty soon… Jeff > On Apr 6, 2015, at 10:42 AM, Jean-Baptiste Onofré wrote: > > Hi all, > > as you may know, codehaus will be down soon: > > http://www.codehaus.org/ > > Even if it's not clear about the future of the IRC server, I think it makes > sense to

Re: [VOTE] Release Apache Camel 2.13.3

+1 Jeff > On Oct 28, 2014, at 12:54 PM, Christian Müller > wrote: > > This is a vote to release Apache Camel 2.13.3, a patch release coming with > about 103 issues fixed. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12327165 >

Re: [VOTE] Release Apache Camel 2.12.5 - second try

+1 Jeff > On Oct 24, 2014, at 9:17 AM, Christian Müller > wrote: > > This is a vote to release Apache Camel 2.12.5, a patch release coming with > about 74 issues fixed. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12327166 > > Staging

Re: [VOTE] Release Apache Camel 2.12.5

+1 Jeff > On Oct 22, 2014, at 11:14 PM, Christian Müller > wrote: > > This is a vote to release Apache Camel 2.12.5, a patch release coming with > about 74 issues fixed. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12327166 > > Stagin

Re: git commit: CAMEL-7023: Added hawtio goal to camel maven plugin.

I will submit my -1 as well. This is not a political discussion, it is technical and Dan's points are indeed technical. I would suggest that any political lines that have appeared to have been drawn here are taken to private@ and need to be worked out there. This is no place to be opining on the

Re: [VOTE] Release Apache Camel 2.11.2

+1 Jeff On Sep 19, 2013, at 3:24 PM, Christian Müller wrote: > After 2 month of development, we have a new bug fix release candidate > apache-camel-2.11.2 ready. > It comes with 120 issues resolved: new features, improvements and bug fixes > [1]. You can find the release notes here [2]. > > P

Re: [VOTE] Release Apache Camel 2.12.1

+1 Jeff On Sep 18, 2013, at 11:25 PM, Christian Müller wrote: > After 9 days of development, we have a new bug fix release candidate > apache-camel-2.12.1 ready. > It comes with 47 issues resolved: new features, improvements and bug fixes > [1]. You can find the release notes here [2]. > > We

Re: [VOTE] Release Apache Camel 2.10.7

+1 Jeff On Sep 15, 2013, at 3:25 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]. > Thi

Re: [VOTE] Release Apache Camel 2.10.6

+1 Jeff On Jul 1, 2013, at 4:01 PM, Christian Müller wrote: > To address CVE-2013-2160 [1], we have a new bug fix release candidate > apache-camel-2.10.6 ready. This bug fix was necessary, because the Apache > Camel feature descriptor for Apache Karaf was still using Apache CXF > 2.6.6.1. Thi

Re: [VOTE] Release Apache Camel 2.10.5

+1 Jeff On Jun 24, 2013, at 6:35 AM, Ashwin Karpe wrote: > +1 > > > > From: Christian Müller > To: "dev@camel.apache.org" ; "priv...@camel.apache.org" > > Sent: Sunday, June 23, 2013 4:35 AM > Subject: [VOTE] Release Apache Camel 2.10.5 > > > After 4 mon

Re: [VOTE] Release Apache Camel 2.9.7

+1 Jeff -- View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-9-7-tp5731493p5731495.html Sent from the Camel Development mailing list archive at Nabble.com.

Re: [VOTE] Release Apache Camel 2.11.0 (take 4)

+1 Jeff -- View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-0-take-4-tp5731040p5731042.html Sent from the Camel Development mailing list archive at Nabble.com.

Re: [VOTE] Release Apache Camel 2.10.2

+1 Jeff -- View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-10-2-tp5720929p5720973.html Sent from the Camel Development mailing list archive at Nabble.com.

Re: [VOTE] Camel MUST use valid URIs for identifying and configuring Endpoints

I'm not sure if my last email made it through since I did it through Nabble... But I had followed up with wondering why this URI stuff cannot be an additional style URI parse that is in addition to what is being done today. Is there a technical reason why we cannot support both styles of URLs, th

Re: [VOTE] Camel MUST use valid URIs for identifying and configuring Endpoints

+1 - This has been a common complaint from a lot of users about not being a standard. We just did a presentation and had people raising their hands asking why they are so different. I think this would be great. -- View this message in context: http://camel.465427.n5.nabble.com/VOTE-Camel-MUST-u

[jira] [Commented] (CAMEL-4345) Synchronized code causes long delays and hangs for big applications especially with Blueprint

[ https://issues.apache.org/jira/browse/CAMEL-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087662#comment-13087662 ] Jeff Genender commented on CAMEL-4345: -- Claus, yes I opened an issue to OSGI

[jira] [Updated] (CAMEL-4345) Synchronized code causes long delays and hangs for big applications especially with Blueprint

[ https://issues.apache.org/jira/browse/CAMEL-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Genender updated CAMEL-4345: - Attachment: CAMEL-4345.patch Patch attached against TRUNK as of r1158987 > Synchronized c

[jira] [Created] (CAMEL-4345) Synchronized code causes long delays and hangs for big applications especially with Blueprint

Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.8.0 Environment: Linux and Mac multicore machines Reporter: Jeff Genender The DefaultCamelContext uses synchronized "endpoints" which ends up ultimately e

[jira] Updated: (CAMEL-2445) BatchProcesser.processExchange needs to catch Throwable

[ https://issues.apache.org/activemq/browse/CAMEL-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Genender updated CAMEL-2445: - Attachment: 2.x.patch 1.x.patch > BatchProcesser.processExchange needs

[jira] Commented: (CAMEL-2445) BatchProcesser.processExchange needs to catch Throwable

[ https://issues.apache.org/activemq/browse/CAMEL-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57361#action_57361 ] Jeff Genender commented on CAMEL-2445: -- This is caused by the the trapping of Excep