[GitHub] camel pull request #1082: CAMEL-10161 Passthrough headers for outputType=Str...

2016-07-19 Thread drsquidop
GitHub user drsquidop opened a pull request: https://github.com/apache/camel/pull/1082 CAMEL-10161 Passthrough headers for outputType=StreamList You can merge this pull request into a Git repository by running: $ git pull https://github.com/drsquidop/camel CAMEL-10161 Alterna

Camel.trunk.notest build job

2016-07-19 Thread Siano, Stephan
Hi, After my commit yesterday I got a mail that the Camel.trunk.notest job failed. On a first look I found out that it failed with an OOM in the camel-olingo component (so I would guess that it is completely unrelated to any recent check-in but more like a job-setup issue). On a second look I f

Camel.trunk.notest - Build # 2817 - Still Failing

2016-07-19 Thread Apache Jenkins Server
The Apache Jenkins build system has built Camel.trunk.notest (build #2817) Status: Still Failing Check console output at https://builds.apache.org/job/Camel.trunk.notest/2817/ to view the results.

[GitHub] camel pull request #1081: https://issues.apache.org/jira/browse/CAMEL-10158

2016-07-19 Thread ssharma
GitHub user ssharma opened a pull request: https://github.com/apache/camel/pull/1081 https://issues.apache.org/jira/browse/CAMEL-10158 Support to add tags to workflow execution in camel-aws component You can merge this pull request into a Git repository by running: $ git pull h

RE: [DISCUSS] Attachment Headers

2016-07-19 Thread Siano, Stephan
Thanks for the pointer. -Original Message- From: Claus Ibsen [mailto:claus.ib...@gmail.com] Sent: Dienstag, 19. Juli 2016 13:08 To: dev Subject: Re: [DISCUSS] Attachment Headers Just edit the release notes at http://camel.apache.org/camel-2180-release.html You are welcome to create a n

Re: [DISCUSS] Attachment Headers

2016-07-19 Thread Claus Ibsen
Just edit the release notes at http://camel.apache.org/camel-2180-release.html You are welcome to create a new wiki page with more details, such as the heads up email you wrote, and then link from the release notes to this wiki page. On Tue, Jul 19, 2016 at 12:55 PM, Siano, Stephan wrote: > Hi C

RE: [DISCUSS] Attachment Headers

2016-07-19 Thread Siano, Stephan
Hi Claus, How do I provide input for the 2.18 release notes? Best regards Stephan -Original Message- From: Claus Ibsen [mailto:claus.ib...@gmail.com] Sent: Dienstag, 19. Juli 2016 11:56 To: dev Subject: Re: [DISCUSS] Attachment Headers Hi Sounds good. Javadoc is good for documenting

[HEADS UP] Extensions for attachments in master branch

2016-07-19 Thread Siano, Stephan
Hi, I have just checked an extension for the attachment handling into the master (2.18) branch. As long as you don't use attachments you will very likely not notice any difference. If you have created an implementation of the Message interface that does not extend DefaultMessage, you will need

RE: [DISCUSS] Attachment Headers

2016-07-19 Thread Bharath Kumar Champalal
That can be done in GIthub too. Since that supports. -Original Message- From: Bharath Kumar Champalal Sent: Tuesday, July 19, 2016 3:39 PM To: dev Subject: RE: [DISCUSS] Attachment Headers That would be gr8. Can we have Doxygen as an option They support Markdown, which looks nice. --

RE: [DISCUSS] Attachment Headers

2016-07-19 Thread Bharath Kumar Champalal
That would be gr8. Can we have Doxygen as an option They support Markdown, which looks nice. -Original Message- From: Claus Ibsen [mailto:claus.ib...@gmail.com] Sent: Tuesday, July 19, 2016 3:26 PM To: dev Subject: Re: [DISCUSS] Attachment Headers Hi Sounds good. Javadoc is good for

Re: [DISCUSS] Attachment Headers

2016-07-19 Thread Claus Ibsen
Hi Sounds good. Javadoc is good for documenting this kind of APIs. Some details on the 2.18 release note would be good. And good idea with the [HEADS UP]. When we get rid of the wiki documentation and document from the source with the ascii doc which we also tie to a new website, then its a good