[GitHub] camel pull request #669: Allow to use different registries in tests.

[pwojnowski]

Github user pwojnowski closed the pull request at:

https://github.com/apache/camel/pull/669


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] camel pull request #1162: CAMEL-10298: Remove readLockTimeout check from rea...

[yuruki]

GitHub user yuruki opened a pull request:

https://github.com/apache/camel/pull/1162

CAMEL-10298: Remove readLockTimeout check from readLockMinAge

https://issues.apache.org/jira/browse/CAMEL-10298

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yuruki/camel camel-readlockminage

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1162.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1162


commit 3ce77320493fb680570c3e4a31f8a276052d4255
Author: Jyrki Ruuskanen 
Date:   2016-09-08T11:03:00Z

CAMEL-10298: Remove readLockTimeout check from readLockMinAge




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] camel pull request #1163: CAMEL-10298: Remove readLockTimeout check from rea...

[yuruki]

GitHub user yuruki opened a pull request:

https://github.com/apache/camel/pull/1163

CAMEL-10298: Remove readLockTimeout check from readLockMinAge (2.17.x)

https://issues.apache.org/jira/browse/CAMEL-10298

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yuruki/camel camel-readlockminage-2.17.x

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1163.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1163


commit a0cd47f5695116776c216dcdc9a0ff0f8f7054b0
Author: Jyrki Ruuskanen 
Date:   2016-09-08T11:34:32Z

CAMEL-10298: Remove readLockTimeout check from readLockMinAge (2.17.x)




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Java8 DSL (CAMEL-7831)

[Claus Ibsen]

Looks good Luca.

Great to have this experimental DSL in the release so we can show it
to end users and get feedback.

Would be good with a camel-example-java8 as an example using the DSL.


On Tue, Sep 6, 2016 at 5:37 PM, Luca Burgazzoli  wrote:
> Hello everyone,
> I've started working on CAMEL-7831 to create a Java8 example to use
> Expressions and I've ended up with a simple example - see [1].
> Of course it is only for demonstrative purpose.
>
> Java8 lambda support to Expressions has been added to
> - ExpressionClause to avoid adding overload method for every method
> accepting an Expressions definition
> - ExpressionBuilder so you can use something like transform(function(e -> 
> ...))
>
> There are some additional functional interfaces to select the argument
> of the lambda
> - ExchangeFunction
> - MessageFunction
> - BodyFunction
>
>
> Any feedback would be really appreciated.
>
> Regards,
> Luca
>
>
> [1] 
> https://github.com/lburgazzoli/apache-camel/blob/CAMEL-7831/examples/camel-example-dsl-java8/src/main/java/org/apache/camel/example/dsl/java8/MyRoute.java
>
>
> ---
> Luca Burgazzoli



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Help adding logic to camel component that executes before onComplete

[Quinn Stevenson]

I made some progress with this.  

In my SynchronizationAdapter, I had been calling exchange.getIn().setHeader(…) 
- I’d never looked to see if there was an “out” message.  Once I changed this 
to set the header on the out message, the headers started showing up where I 
wanted them.

Now I’m down to error handling.  If something goes wrong during the 
acknowledgement, I can set an exception on the exchange and than the route 
knows that the exchanged failed - I tested this with an 
onCompletion.onFailureOnly element.

However, the exchanged passed to the onCompletion.onFailureOnly element does 
NOT have the exception set - so I’m not sure how the route is supposed to tell 
what happened.  Do I need to do more than just set the exception on the 
exchange?

Also, is there a way to get Camel’s error handling to kick-in after the 
SyncronizationAdapter sets the exception on the exchange?

> On Sep 6, 2016, at 5:06 PM, Quinn Stevenson  
> wrote:
> 
> I’m struggling with this, and I can’t seem to get what I’m after.
> 
> I added a SynchronizationAdapter (via addOnCompletion), but the exchange 
> passed to the onComplete portion of the route still doesn’t have the headers 
> I’m setting in the Syncronizationadapter.  I’ve tried setting the header in 
> both the onAfterRoute and onComplete methods, but no luck.  The only place 
> that seems to work is if I add the header in the onBeforeRoute method, but I 
> don’t have enough information at that point to set the header correctly.
> 
> The other thing I’d tried previously that I thought would work was simply 
> setting the headers in the Consumer, after it called 
> getProcessor().process(exchange) - but that doesn’t work either.  I’m not 
> sure why that doesn’t work - I set headers before I call 
> getProcessor().process(exchange), and they behave as I’d expect.  However, 
> anything I do to the exchange after I call getProcessor().process(exchange) 
> doesn’t seem to have any effect?
> 
> Maybe I need to do something different than just call 
> getProcessor().process(exchange)?  Somehow intercept the flow of the exchange 
> after the last processor in the route, but before before camel does whatever 
> it does that makes my copy of the exchange irrelevant?
> 
> 
>> On Sep 6, 2016, at 2:02 PM, Claus Ibsen  wrote:
>> 
>> There is an addOnCompletion on the exchange you can use. Then your
>> onCompletion can implement that interface, or extend
>> SynchronizationAdapter
>> 
>> On Tue, Sep 6, 2016 at 9:52 PM, Quinn Stevenson
>>  wrote:
>>> Thank you for the prompt reply :-)
>>> 
>>> This sounds like exactly what I need, but I’m a little unclear about how to 
>>> implement it.  I tried creating a UnitOfWork, adding a Synchronization, and 
>>> then setting the UnitOfWork on the exchange when I create it, but my 
>>> Synchronization isn’t getting called.
>>> 
>>> is there another component somewhere that does something similar that I 
>>> could look at?
>>> 
>>> 
 On Sep 6, 2016, at 1:25 PM, Claus Ibsen  wrote:
 
 If you talk about UoW completions with Synchronization:
 org.apache.camel.spi.Synchronization
 
 Then you can implement Ordered, and then set the value to be HIGHEST
 so this one is run before the others.
 
 
 On Tue, Sep 6, 2016 at 9:20 PM, Quinn Stevenson
  wrote:
> I would like to enhance the camel-mllp component to set a message header 
> containing the MLLP Acknowledgement when the component is automatically 
> generating the acknowledgment.  This code would need to execute after the 
> last element in the main route, but before any onCompletion elements are 
> invoked, but I can’t figure out the right way to make this happen.
> 
> Can someone point me in the right direction?
> 
> 
 
 
 
 --
 Claus Ibsen
 -
 http://davsclaus.com @davsclaus
 Camel in Action 2: https://www.manning.com/ibsen2
>>> 
>> 
>> 
>> 
>> -- 
>> Claus Ibsen
>> -
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
> 

Re: Help adding logic to camel component that executes before onComplete

[Claus Ibsen]

On Thu, Sep 8, 2016 at 3:36 PM, Quinn Stevenson
 wrote:
> I made some progress with this.
>
> In my SynchronizationAdapter, I had been calling 
> exchange.getIn().setHeader(…) - I’d never looked to see if there was an “out” 
> message.  Once I changed this to set the header on the out message, the 
> headers started showing up where I wanted them.
>

You can use hasOut() to check if there is OUT message or not.

> Now I’m down to error handling.  If something goes wrong during the 
> acknowledgement, I can set an exception on the exchange and than the route 
> knows that the exchanged failed - I tested this with an 
> onCompletion.onFailureOnly element.
>
> However, the exchanged passed to the onCompletion.onFailureOnly element does 
> NOT have the exception set - so I’m not sure how the route is supposed to 
> tell what happened.  Do I need to do more than just set the exception on the 
> exchange?
>

There is a FAQ about this
http://camel.apache.org/why-is-the-exception-null-when-i-use-onexception.html

> Also, is there a way to get Camel’s error handling to kick-in after the 
> SyncronizationAdapter sets the exception on the exchange?
>
>> On Sep 6, 2016, at 5:06 PM, Quinn Stevenson  
>> wrote:
>>
>> I’m struggling with this, and I can’t seem to get what I’m after.
>>
>> I added a SynchronizationAdapter (via addOnCompletion), but the exchange 
>> passed to the onComplete portion of the route still doesn’t have the headers 
>> I’m setting in the Syncronizationadapter.  I’ve tried setting the header in 
>> both the onAfterRoute and onComplete methods, but no luck.  The only place 
>> that seems to work is if I add the header in the onBeforeRoute method, but I 
>> don’t have enough information at that point to set the header correctly.
>>
>> The other thing I’d tried previously that I thought would work was simply 
>> setting the headers in the Consumer, after it called 
>> getProcessor().process(exchange) - but that doesn’t work either.  I’m not 
>> sure why that doesn’t work - I set headers before I call 
>> getProcessor().process(exchange), and they behave as I’d expect.  However, 
>> anything I do to the exchange after I call getProcessor().process(exchange) 
>> doesn’t seem to have any effect?
>>
>> Maybe I need to do something different than just call 
>> getProcessor().process(exchange)?  Somehow intercept the flow of the 
>> exchange after the last processor in the route, but before before camel does 
>> whatever it does that makes my copy of the exchange irrelevant?
>>
>>
>>> On Sep 6, 2016, at 2:02 PM, Claus Ibsen  wrote:
>>>
>>> There is an addOnCompletion on the exchange you can use. Then your
>>> onCompletion can implement that interface, or extend
>>> SynchronizationAdapter
>>>
>>> On Tue, Sep 6, 2016 at 9:52 PM, Quinn Stevenson
>>>  wrote:
 Thank you for the prompt reply :-)

 This sounds like exactly what I need, but I’m a little unclear about how 
 to implement it.  I tried creating a UnitOfWork, adding a Synchronization, 
 and then setting the UnitOfWork on the exchange when I create it, but my 
 Synchronization isn’t getting called.

 is there another component somewhere that does something similar that I 
 could look at?


> On Sep 6, 2016, at 1:25 PM, Claus Ibsen  wrote:
>
> If you talk about UoW completions with Synchronization:
> org.apache.camel.spi.Synchronization
>
> Then you can implement Ordered, and then set the value to be HIGHEST
> so this one is run before the others.
>
>
> On Tue, Sep 6, 2016 at 9:20 PM, Quinn Stevenson
>  wrote:
>> I would like to enhance the camel-mllp component to set a message header 
>> containing the MLLP Acknowledgement when the component is automatically 
>> generating the acknowledgment.  This code would need to execute after 
>> the last element in the main route, but before any onCompletion elements 
>> are invoked, but I can’t figure out the right way to make this happen.
>>
>> Can someone point me in the right direction?
>>
>>
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2

>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Java8 DSL (CAMEL-7831)

[Luca Burgazzoli]

I'll merge it before eow as well as an archetype and example

---
Luca Burgazzoli


On Thu, Sep 8, 2016 at 3:26 PM, Claus Ibsen  wrote:
> Looks good Luca.
>
> Great to have this experimental DSL in the release so we can show it
> to end users and get feedback.
>
> Would be good with a camel-example-java8 as an example using the DSL.
>
>
> On Tue, Sep 6, 2016 at 5:37 PM, Luca Burgazzoli  wrote:
>> Hello everyone,
>> I've started working on CAMEL-7831 to create a Java8 example to use
>> Expressions and I've ended up with a simple example - see [1].
>> Of course it is only for demonstrative purpose.
>>
>> Java8 lambda support to Expressions has been added to
>> - ExpressionClause to avoid adding overload method for every method
>> accepting an Expressions definition
>> - ExpressionBuilder so you can use something like transform(function(e -> 
>> ...))
>>
>> There are some additional functional interfaces to select the argument
>> of the lambda
>> - ExchangeFunction
>> - MessageFunction
>> - BodyFunction
>>
>>
>> Any feedback would be really appreciated.
>>
>> Regards,
>> Luca
>>
>>
>> [1] 
>> https://github.com/lburgazzoli/apache-camel/blob/CAMEL-7831/examples/camel-example-dsl-java8/src/main/java/org/apache/camel/example/dsl/java8/MyRoute.java
>>
>>
>> ---
>> Luca Burgazzoli
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2

Re: Help adding logic to camel component that executes before onComplete

[Quinn Stevenson]

Thanks for the quick reply Claus -

I always use the hasOut() to figure out what message to work with in my 
processors - I’m not sure why I missed it here the first time around.  I was a 
little surprised about the out message being there (since I don’t explicitly 
use one) - I thought I’d read that the out message was being deprecated, but it 
looks like the core engine is using it in this case.  Anyway, it just 
reinforced my “always use hasOut” habit :-)

I’d seen that FAQ, but it’s talking about onException elements - I can’t get 
the onException elements to fire.  The onCompletion.onCompleteOnly() and 
onCompletion.onFailureOnly are getting fired when I expect, but the onException 
element never gets called.

So does this FAQ apply to onCompletion.onFailureOnly as well?  I just need to 
look for the EXCEPTION_CAUGHT property?  I thought I had, but I’ll re-test to 
make sure.

> On Sep 8, 2016, at 7:41 AM, Claus Ibsen  wrote:
> 
> On Thu, Sep 8, 2016 at 3:36 PM, Quinn Stevenson
> mailto:qu...@pronoia-solutions.com>> wrote:
>> I made some progress with this.
>> 
>> In my SynchronizationAdapter, I had been calling 
>> exchange.getIn().setHeader(…) - I’d never looked to see if there was an 
>> “out” message.  Once I changed this to set the header on the out message, 
>> the headers started showing up where I wanted them.
>> 
> 
> You can use hasOut() to check if there is OUT message or not.
> 
>> Now I’m down to error handling.  If something goes wrong during the 
>> acknowledgement, I can set an exception on the exchange and than the route 
>> knows that the exchanged failed - I tested this with an 
>> onCompletion.onFailureOnly element.
>> 
>> However, the exchanged passed to the onCompletion.onFailureOnly element does 
>> NOT have the exception set - so I’m not sure how the route is supposed to 
>> tell what happened. Do I need to do more than just set the exception on the 
>> exchange?
>> 
> 
> There is a FAQ about this
> http://camel.apache.org/why-is-the-exception-null-when-i-use-onexception.html 
> 
> 
>> Also, is there a way to get Camel’s error handling to kick-in after the 
>> SyncronizationAdapter sets the exception on the exchange?
>> 
>>> On Sep 6, 2016, at 5:06 PM, Quinn Stevenson  
>>> wrote:
>>> 
>>> I’m struggling with this, and I can’t seem to get what I’m after.
>>> 
>>> I added a SynchronizationAdapter (via addOnCompletion), but the exchange 
>>> passed to the onComplete portion of the route still doesn’t have the 
>>> headers I’m setting in the Syncronizationadapter.  I’ve tried setting the 
>>> header in both the onAfterRoute and onComplete methods, but no luck.  The 
>>> only place that seems to work is if I add the header in the onBeforeRoute 
>>> method, but I don’t have enough information at that point to set the header 
>>> correctly.
>>> 
>>> The other thing I’d tried previously that I thought would work was simply 
>>> setting the headers in the Consumer, after it called 
>>> getProcessor().process(exchange) - but that doesn’t work either.  I’m not 
>>> sure why that doesn’t work - I set headers before I call 
>>> getProcessor().process(exchange), and they behave as I’d expect.  However, 
>>> anything I do to the exchange after I call getProcessor().process(exchange) 
>>> doesn’t seem to have any effect?
>>> 
>>> Maybe I need to do something different than just call 
>>> getProcessor().process(exchange)? Somehow intercept the flow of the 
>>> exchange after the last processor in the route, but before before camel 
>>> does whatever it does that makes my copy of the exchange irrelevant?
>>> 
>>> 
 On Sep 6, 2016, at 2:02 PM, Claus Ibsen  wrote:
 
 There is an addOnCompletion on the exchange you can use. Then your
 onCompletion can implement that interface, or extend
 SynchronizationAdapter
 
 On Tue, Sep 6, 2016 at 9:52 PM, Quinn Stevenson
  wrote:
> Thank you for the prompt reply :-)
> 
> This sounds like exactly what I need, but I’m a little unclear about how 
> to implement it.  I tried creating a UnitOfWork, adding a 
> Synchronization, and then setting the UnitOfWork on the exchange when I 
> create it, but my Synchronization isn’t getting called.
> 
> is there another component somewhere that does something similar that I 
> could look at?
> 
> 
>> On Sep 6, 2016, at 1:25 PM, Claus Ibsen  wrote:
>> 
>> If you talk about UoW completions with Synchronization:
>> org.apache.camel.spi.Synchronization
>> 
>> Then you can implement Ordered, and then set the value to be HIGHEST
>> so this one is run before the others.
>> 
>> 
>> On Tue, Sep 6, 2016 at 9:20 PM, Quinn Stevenson
>>  wrote:
>>> I would like to enhance the camel-mllp component to set a message 
>>> header containing the MLLP Acknowledgement when the component is 
>>> automatically generating the acknowledgmen

Re: Help adding logic to camel component that executes before onComplete

[Quinn Stevenson]

I just retested this, and the EXCEPTION_CAUGHT property is NOT on the exchange 
sent to onCompletion.onFailureOnly element.  

So my last question is - can I do something in the SyncronizationAdapter so 
that the onException elements will get triggered?

> On Sep 8, 2016, at 8:23 AM, Quinn Stevenson  
> wrote:
> 
> Thanks for the quick reply Claus -
> 
> I always use the hasOut() to figure out what message to work with in my 
> processors - I’m not sure why I missed it here the first time around.  I was 
> a little surprised about the out message being there (since I don’t 
> explicitly use one) - I thought I’d read that the out message was being 
> deprecated, but it looks like the core engine is using it in this case.  
> Anyway, it just reinforced my “always use hasOut” habit :-)
> 
> I’d seen that FAQ, but it’s talking about onException elements - I can’t get 
> the onException elements to fire.  The onCompletion.onCompleteOnly() and 
> onCompletion.onFailureOnly are getting fired when I expect, but the 
> onException element never gets called.
> 
> So does this FAQ apply to onCompletion.onFailureOnly as well?  I just need to 
> look for the EXCEPTION_CAUGHT property?  I thought I had, but I’ll re-test to 
> make sure.
> 
>> On Sep 8, 2016, at 7:41 AM, Claus Ibsen > > wrote:
>> 
>> On Thu, Sep 8, 2016 at 3:36 PM, Quinn Stevenson
>> mailto:qu...@pronoia-solutions.com>> wrote:
>>> I made some progress with this.
>>> 
>>> In my SynchronizationAdapter, I had been calling 
>>> exchange.getIn().setHeader(…) - I’d never looked to see if there was an 
>>> “out” message.  Once I changed this to set the header on the out message, 
>>> the headers started showing up where I wanted them.
>>> 
>> 
>> You can use hasOut() to check if there is OUT message or not.
>> 
>>> Now I’m down to error handling.  If something goes wrong during the 
>>> acknowledgement, I can set an exception on the exchange and than the route 
>>> knows that the exchanged failed - I tested this with an 
>>> onCompletion.onFailureOnly element.
>>> 
>>> However, the exchanged passed to the onCompletion.onFailureOnly element 
>>> does NOT have the exception set - so I’m not sure how the route is supposed 
>>> to tell what happened. Do I need to do more than just set the exception on 
>>> the exchange?
>>> 
>> 
>> There is a FAQ about this
>> http://camel.apache.org/why-is-the-exception-null-when-i-use-onexception.html
>>  
>> 
>> 
>>> Also, is there a way to get Camel’s error handling to kick-in after the 
>>> SyncronizationAdapter sets the exception on the exchange?
>>> 
 On Sep 6, 2016, at 5:06 PM, Quinn Stevenson >>> > wrote:
 
 I’m struggling with this, and I can’t seem to get what I’m after.
 
 I added a SynchronizationAdapter (via addOnCompletion), but the exchange 
 passed to the onComplete portion of the route still doesn’t have the 
 headers I’m setting in the Syncronizationadapter.  I’ve tried setting the 
 header in both the onAfterRoute and onComplete methods, but no luck.  The 
 only place that seems to work is if I add the header in the onBeforeRoute 
 method, but I don’t have enough information at that point to set the 
 header correctly.
 
 The other thing I’d tried previously that I thought would work was simply 
 setting the headers in the Consumer, after it called 
 getProcessor().process(exchange) - but that doesn’t work either.  I’m not 
 sure why that doesn’t work - I set headers before I call 
 getProcessor().process(exchange), and they behave as I’d expect.  However, 
 anything I do to the exchange after I call 
 getProcessor().process(exchange) doesn’t seem to have any effect?
 
 Maybe I need to do something different than just call 
 getProcessor().process(exchange)? Somehow intercept the flow of the 
 exchange after the last processor in the route, but before before camel 
 does whatever it does that makes my copy of the exchange irrelevant?
 
 
> On Sep 6, 2016, at 2:02 PM, Claus Ibsen  > wrote:
> 
> There is an addOnCompletion on the exchange you can use. Then your
> onCompletion can implement that interface, or extend
> SynchronizationAdapter
> 
> On Tue, Sep 6, 2016 at 9:52 PM, Quinn Stevenson
> mailto:qu...@pronoia-solutions.com>> wrote:
>> Thank you for the prompt reply :-)
>> 
>> This sounds like exactly what I need, but I’m a little unclear about how 
>> to implement it.  I tried creating a UnitOfWork, adding a 
>> Synchronization, and then setting the UnitOfWork on the exchange when I 
>> create it, but my Synchronization isn’t getting called.
>> 
>> is there another component somewhere that does something similar that I 
>> could look at?
>> 
>> 
>>> On 

Re: Getting ready for Apache Camel 2.18 Release

[Walzer, Thomas]

Hi, Quinn,

I took a look at PR987:

1) the parent pom should be something like 2.18.0 not 2.18 (maybe the PR was 
around too long, so the parent changed).
2) The readme really needs some love. It mentions spring when there is really 
blueprint; jms, when there is none, etc.
3) for me an example replacing/redefining jms: or activemq: by seda: would 
really make a difference. Like having a jms-definitions-bp.xml and then 
replacing it by seda-definitions-bp.xml, or something like that. I know that´s 
not the point of your sample but the timer-example seems a bit basic. 
4) maybe …-test-karaf would be a better name?
5) my unit tests and itests do not run through. If they would I could provide 
more fleshy feedback.

If I can help, let me know.

Cheers, Thomas.

---
 T E S T S
---
Running org.apache.camel.BlueprintBeanPropertiesOverrideFromFileTest
Unable to start bundle: org.apache.felix.gogo.runtime [64]
org.osgi.framework.BundleException: Unable to start bundle
at org.apache.felix.connect.PojoSRBundle.start(PojoSRBundle.java:163)
at org.apache.felix.connect.PojoSR.startBundles(PojoSR.java:304)
at org.apache.felix.connect.PojoSR.(PojoSR.java:248)
at org.apache.felix.connect.PojoSR.(PojoSR.java:129)
at 
org.apache.felix.connect.PojoServiceRegistryFactoryImpl.newPojoServiceRegistry(PojoServiceRegistryFactoryImpl.java:52)
at 
org.apache.camel.test.blueprint.CamelBlueprintHelper.createBundleContext(CamelBlueprintHelper.java:173)
at 
org.apache.camel.test.blueprint.CamelBlueprintHelper.createBundleContext(CamelBlueprintHelper.java:119)
at 
org.apache.camel.test.blueprint.CamelBlueprintTestSupport.createBundleContext(CamelBlueprintTestSupport.java:127)
at 
org.apache.camel.test.blueprint.CamelBlueprintTestSupport.setUp(CamelBlueprintTestSupport.java:241)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
Caused by: java.lang.IllegalStateException: Thread Print Stream already set
at 
org.apache.felix.gogo.runtime.threadio.ThreadIOImpl.start(ThreadIOImpl.java:49)
at 
org.apache.felix.gogo.runtime.activator.Activator.start(Activator.java:76)
at org.apache.felix.connect.PojoSRBundle.start(PojoSRBundle.java:153)
... 37 more
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.485 sec - in 
org.apache.camel.BlueprintBeanPropertiesOverrideFromFileTest
Running org.apache.camel.BlueprintBeanPropertiesOverrideFromTestTest
Unable to sta

Camel.trunk.notest - Build # 2868 - Failure

[Apache Jenkins Server]

The Apache Jenkins build system has built Camel.trunk.notest (build #2868)

Status: Failure

Check console output at https://builds.apache.org/job/Camel.trunk.notest/2868/ 
to view the results.

building camel code (init eclipse workspace)

[fabryprog]

Hello,

i am trying to build source code (master - 8 sept 2016) from this page:
http://camel.apache.org/building.html

i would use eclipse (neon) so i execute this command: 

mvn -Psetup.eclipse -Declipse.workspace.dir=/path/to/your/workspace

zZzzZZzzz

after 15 minutes this is the output

[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 02:34 min
[INFO] Finished at: 2016-09-08T23:07:29+02:00
[INFO] Final Memory: 1034M/2886M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-eclipse-plugin:2.10:eclipse
(setup.eclipse.project) on project camel-test-karaf: Unable to resolve
resource location: /camel-eclipse-checkstyle -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :camel-test-karaf



Can you help me? 

King regards



--
View this message in context: 
http://camel.465427.n5.nabble.com/building-camel-code-init-eclipse-workspace-tp5787394.html
Sent from the Camel Development mailing list archive at Nabble.com.

Re: building camel code (init eclipse workspace)

[Antoine Toulme]

From experience, you probably want to go the m2e way and import the projects as 
Maven projects.

> On Sep 8, 2016, at 2:18 PM, fabryprog  wrote:
> 
> Hello,
> 
> i am trying to build source code (master - 8 sept 2016) from this page:
> http://camel.apache.org/building.html
> 
> i would use eclipse (neon) so i execute this command:
> 
> mvn -Psetup.eclipse -Declipse.workspace.dir=/path/to/your/workspace
> 
> zZzzZZzzz
> 
> after 15 minutes this is the output
> 
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 02:34 min
> [INFO] Finished at: 2016-09-08T23:07:29+02:00
> [INFO] Final Memory: 1034M/2886M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-eclipse-plugin:2.10:eclipse
> (setup.eclipse.project) on project camel-test-karaf: Unable to resolve
> resource location: /camel-eclipse-checkstyle -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :camel-test-karaf
> 
> 
> 
> Can you help me?
> 
> King regards
> 
> 
> 
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/building-camel-code-init-eclipse-workspace-tp5787394.html
> Sent from the Camel Development mailing list archive at Nabble.com.



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: building camel code (init eclipse workspace)

[Claus Ibsen]

On Fri, Sep 9, 2016 at 8:48 AM, Antoine Toulme  wrote:
> From experience, you probably want to go the m2e way and import the projects 
> as Maven projects.
>

Yeah do not use the maven plugin to create eclipse project files.
Eclipse has out of the box support for maven, so just import the
project directly in Eclipse. And mind the Camel source code is big, so
you better just import only the module you want such as camel-core, or
camel-http or what module you look into.



>> On Sep 8, 2016, at 2:18 PM, fabryprog  wrote:
>>
>> Hello,
>>
>> i am trying to build source code (master - 8 sept 2016) from this page:
>> http://camel.apache.org/building.html
>>
>> i would use eclipse (neon) so i execute this command:
>>
>> mvn -Psetup.eclipse -Declipse.workspace.dir=/path/to/your/workspace
>>
>> zZzzZZzzz
>>
>> after 15 minutes this is the output
>>
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 02:34 min
>> [INFO] Finished at: 2016-09-08T23:07:29+02:00
>> [INFO] Final Memory: 1034M/2886M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-eclipse-plugin:2.10:eclipse
>> (setup.eclipse.project) on project camel-test-karaf: Unable to resolve
>> resource location: /camel-eclipse-checkstyle -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
>> switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions, please
>> read the following articles:
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>> [ERROR]   mvn  -rf :camel-test-karaf
>>
>>
>>
>> Can you help me?
>>
>> King regards
>>
>>
>>
>> --
>> View this message in context: 
>> http://camel.465427.n5.nabble.com/building-camel-code-init-eclipse-workspace-tp5787394.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
>



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2