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 d
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
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]
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.
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 re
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 Stevenso
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 th
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
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
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
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-78
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 p
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 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 e
14 matches
Mail list logo
