[jira] [Created] (CAMEL-4332) camel-nagios - Use Camel type converter to convert message body to String before sending to Nagios

camel-nagios - Use Camel type converter to convert message body to String before sending to Nagios -- Key: CAMEL-4332 URL:

[jira] [Assigned] (CAMEL-4331) Avoid the redundant direct dependency on log4j by the components (of the scope 'test'), as it's transitively given for free through the slf4j-log4j12 dependency with the

[ https://issues.apache.org/jira/browse/CAMEL-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-4331: -- Assignee: Claus Ibsen Avoid the redundant direct dependency on log4j by the components (of

[DISCUSS] - Dropping Maven 2.x support

Hi I wonder if we should consider dropping any official support for Maven 2.x on the Apache Camel project? I guess most people is now migrated to Maven 3.0. And the last number of releases has been done using Maven 3.0.x. Also in light of JDK 7 is now GA, and thus there could be issues with old

[jira] [Resolved] (CAMEL-4202) camel-jms - Using request/reply over persistent queues should be faster

[ https://issues.apache.org/jira/browse/CAMEL-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4202. Resolution: Fixed Updated wiki page with documentation camel-jms - Using request/reply over

Jenkins build is back to normal : Camel #1301

See https://builds.apache.org/job/Camel/1301/changes

[jira] [Created] (CAMEL-4333) Add wereSentTo to NotifyBuilder to match if exchange was sent to the given endpoint pattern

Add wereSentTo to NotifyBuilder to match if exchange was sent to the given endpoint pattern --- Key: CAMEL-4333 URL: https://issues.apache.org/jira/browse/CAMEL-4333

[jira] [Resolved] (CAMEL-4333) Add wereSentTo to NotifyBuilder to match if exchange was sent to the given endpoint pattern

[ https://issues.apache.org/jira/browse/CAMEL-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4333. Resolution: Fixed Add wereSentTo to NotifyBuilder to match if exchange was sent to the given

[jira] [Created] (CAMEL-4334) ResourceHelperTest.testLoadFileNotFound fails in Windows/non english OS.

ResourceHelperTest.testLoadFileNotFound fails in Windows/non english OS. Key: CAMEL-4334 URL: https://issues.apache.org/jira/browse/CAMEL-4334 Project: Camel Issue

Re: [DISCUSS] - Dropping Maven 2.x support

I think it's the right way and the right time to do it. Then we can also upgrade the plugins, which doesn't work with Maven 3, e.g. 'maven-shade-plugin'. Christian

Re: [DISCUSS] - Dropping Maven 2.x support

+1 On Sun, Aug 14, 2011 at 5:17 PM, Christian Müller christian.muel...@gmail.com wrote: I think it's the right way and the right time to do it. Then we can also upgrade the plugins, which doesn't work with Maven 3, e.g. 'maven-shade-plugin'. Christian

Re: [DISCUSS] - Dropping Maven 2.x support

+1, sounds like one less thing to worry about. /je

Re: [DISCUSS] - Adjust Apache Camel product descriptions

+1 to remove the descriptions of the Spring based. On 8/13/11 7:14 PM, Claus Ibsen wrote: Hi I noticed the README.txt file in the distribution kit starts as follows: Apache Camel is a powerful Spring based Integration Framework. And our website starts as follows: Apache Camel is a powerful

Re: [DISCUSS] - Adjust Apache Camel product descriptions

We could even say we are not spring based, as we are focused on providing an integration library that will co-exist in pretty much any container, deployment environment as well. /je On Aug 14, 2011, at 8:12 PM, Willem Jiang wrote: +1 to remove the descriptions of the Spring based. On

Re: [DISCUSS] - Dropping Maven 2.x support

+1 Freeman On 2011-8-14, at 下午5:35, Claus Ibsen wrote: Hi I wonder if we should consider dropping any official support for Maven 2.x on the Apache Camel project? I guess most people is now migrated to Maven 3.0. And the last number of releases has been done using Maven 3.0.x. Also in light

Re: [DISCUSS] - Adjust Apache Camel product descriptions

On 2011-8-13, at 下午7:14, Claus Ibsen wrote: Hi I noticed the README.txt file in the distribution kit starts as follows: Apache Camel is a powerful Spring based Integration Framework. And our website starts as follows: Apache Camel is a powerful open source integration framework based on

[jira] [Commented] (CAMEL-4334) ResourceHelperTest.testLoadFileNotFound fails in Windows/non english OS.

[ https://issues.apache.org/jira/browse/CAMEL-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084969#comment-13084969 ] Claus Ibsen commented on CAMEL-4334: Thanks for reporting. A patch without the

[jira] [Updated] (CAMEL-4334) ResourceHelperTest.testLoadFileNotFound fails in Windows/non english OS.

[ https://issues.apache.org/jira/browse/CAMEL-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-4334: --- Regression: [Unit Test Broken] Issue Type: Test (was: Bug)