[GitHub] camel pull request: CAMEL-9330 : Main - enableHangupSupport should...

Github user lburgazzoli closed the pull request at: https://github.com/apache/camel/pull/765 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] camel pull request: CAMEL-9508 : support jms 2.0 in osgi manifest

Github user yogeshrao closed the pull request at: https://github.com/apache/camel/pull/774 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] camel pull request: [CAMEL-9518] Swagger may see non-camel MBeans

GitHub user tdiesler opened a pull request: https://github.com/apache/camel/pull/775 [CAMEL-9518] Swagger may see non-camel MBeans You can merge this pull request into a Git repository by running: $ git pull https://github.com/tdiesler/camel CAMEL-9518 Alternatively you can

[GitHub] camel pull request: [CAMEL-9518] Swagger may see non-camel MBeans

Github user tdiesler closed the pull request at: https://github.com/apache/camel/pull/775 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Potential Bug in CamelBlueprintTestSupport

Hello Quinn Hmm... I've run `for n in `seq 1 30`; do echo $n; mvn test -Dtest=ConfigAdminLoadConfigurationFileAndOverrideTest|grep BUILD; done` after moving `configadmin-loadfileoverride.xml` from src/test/resources to src/main/resources and everything is fine. Are you doing it in your own

[GitHub] camel pull request: Avoid non-static nested class and fix CS error

Github user astefanutti closed the pull request at: https://github.com/apache/camel/pull/776 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Camel CDI component improvements

Hi Yay this is great news for users who want a microservice kinda way with just a simple cdi dependency injection framework. It would be cool to have a camel-test-cdi module separated from camel-cdi so we have similar "easy of testing" as with the other testing modules. On Thu, Jan 14, 2016 at

[GitHub] camel pull request: Avoid non-static nested class and fix CS error

GitHub user astefanutti opened a pull request: https://github.com/apache/camel/pull/776 Avoid non-static nested class and fix CS error You can merge this pull request into a Git repository by running: $ git pull https://github.com/astefanutti/camel CAMEL-9330 Alternatively

Re: Camel CDI component improvements

Yes, I focused on the core Camel CDI component. I’ll work then on the testing module, samples and documentation. So much to do :) > On 15 Jan 2016, at 14:44, Claus Ibsen wrote: > > Hi > > Yay this is great news for users who want a microservice kinda way > with just a

[GitHub] camel pull request: CAMEL-9201: Improved Camel CDI component

Github user asfgit closed the pull request at: https://github.com/apache/camel/pull/769 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Potential Bug in CamelBlueprintTestSupport

Weird ;) I'll check it - sounds interesting! regards Grzegorz 2016-01-15 17:16 GMT+01:00 Quinn Stevenson : > Hi Grzegorz - > > Sorry I missed you on the IRC - I left my client open last night. > > I put the project I’m using on GitHub >

[GitHub] camel pull request: Remove unecessary inline import

GitHub user astefanutti opened a pull request: https://github.com/apache/camel/pull/777 Remove unecessary inline import You can merge this pull request into a Git repository by running: $ git pull https://github.com/astefanutti/camel CAMEL-9201 Alternatively you can review

Re: Potential Bug in CamelBlueprintTestSupport

Hi Grzegorz - Sorry I missed you on the IRC - I left my client open last night. I put the project I’m using on GitHub https://github.com/hqstevenson/camel-blueprint-test-properties.git The results for me are indeterminate -

Re: Potential Bug in CamelBlueprintTestSupport

Thank You Grzegorz!! I created the sample project using the camel-archetype-blueprint, and it introduced that configuration. I’ve verified that the configuration for the maven-bundle-plugin changed between v 2.14 and 2.15.0. I created https://issues.apache.org/jira/browse/CAMEL-9519

Re: Potential Bug in CamelBlueprintTestSupport

The problem is that your example lead to two bundles in felix-connect OSGi registy: 2016-01-15 18:32:54,172 DEBUG CamelBlueprintHelper - Bundle #0 ->

[GitHub] camel pull request: Fix camel-netty-http unit tests that use 0.0.0...

GitHub user veithen opened a pull request: https://github.com/apache/camel/pull/778 Fix camel-netty-http unit tests that use 0.0.0.0 as target address You can merge this pull request into a Git repository by running: $ git pull https://github.com/veithen/camel

[GitHub] camel pull request: Fix camel-netty4-http unit tests that use 0.0....

Github user veithen closed the pull request at: https://github.com/apache/camel/pull/766 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Camel unit tests - Automatic re-run failed tests

Hi, Though for the moment we have to reject the PR. -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Friday, January 15, 2016 9:01 AM, Claus Ibsen

Re: Camel unit tests - Automatic re-run failed tests

Hi There has been some sporadic errors in camel-netty4-http after a commit change a while back. I suspect there is a race condition in some close channel code that can cause it to fail some tests. Though if the re-run was applied it may hide this problem. The CI tests is pretty good as-is, if