[GitHub] camel pull request #1612: CAMEL-10947 Fixed missing alignment on ${htmlunit-...

2017-04-10 Thread igarashitm
Github user igarashitm closed the pull request at: https://github.com/apache/camel/pull/1612 --- 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 #1612: CAMEL-10947 Fixed missing alignment on ${htmlunit-...

2017-04-10 Thread igarashitm
GitHub user igarashitm opened a pull request: https://github.com/apache/camel/pull/1612 CAMEL-10947 Fixed missing alignment on ${htmlunit-version} property You can merge this pull request into a Git repository by running: $ git pull https://github.com/igarashitm/camel CAMEL-10

Camel.trunk.notest - Build # 3126 - Failure

2017-04-10 Thread Apache Jenkins Server
The Apache Jenkins build system has built Camel.trunk.notest (build #3126) Status: Failure Check console output at https://builds.apache.org/job/Camel.trunk.notest/3126/ to view the results.

Re: Contributing a set of IoT related components

2017-04-10 Thread Jens Reimann
I started PR 1611 [1] as a base of discussion for "Camel Milo". [1] https://github.com/apache/camel/pull/1611 On Fri, Apr 7, 2017 at 9:27 PM, Onder SEZGIN wrote: > nice to hear that more iot support will come into camel. > > i'd be more than happy to contribute the. where i can. > > On Fri, 7 A

[GitHub] camel pull request #1611: Initial import of Camel Milo

2017-04-10 Thread ctron
GitHub user ctron opened a pull request: https://github.com/apache/camel/pull/1611 Initial import of Camel Milo Signed-off-by: Jens Reimann You can merge this pull request into a Git repository by running: $ git pull https://github.com/ctron/camel feature/camel_milo_1 Alterna

[GitHub] camel pull request #1610: CAMEL-10947: camel-box - Upgrade to log4j2 and fix...

2017-04-10 Thread tadayosi
Github user tadayosi closed the pull request at: https://github.com/apache/camel/pull/1610 --- 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 en

[GitHub] camel pull request #1610: CAMEL-10947: camel-box - Upgrade to log4j2 and fix...

2017-04-10 Thread tadayosi
GitHub user tadayosi opened a pull request: https://github.com/apache/camel/pull/1610 CAMEL-10947: camel-box - Upgrade to log4j2 and fix Karaf feature https://issues.apache.org/jira/browse/CAMEL-10947 You can merge this pull request into a Git repository by running: $ git pull

Re: [DISCUSS] - New Apache Camel Logo - Move on with the procedure

2017-04-10 Thread Claus Ibsen
Hi Yes this sounds good to me. On Mon, Apr 10, 2017 at 12:14 PM, Zoran Regvart wrote: > >> On 10 Apr 2017, at 10:43, Claus Ibsen wrote: >> >> I suggest to put the word about about the logo vote will start at X >> and last until Y. >> But I suggest to do this post 2.19 release. >> >> For exam

Re: [DISCUSS] - New Apache Camel Logo - Move on with the procedure

2017-04-10 Thread Zoran Regvart
> On 10 Apr 2017, at 10:43, Claus Ibsen wrote: > > I suggest to put the word about about the logo vote will start at X > and last until Y. > But I suggest to do this post 2.19 release. > > For example start May 1st until May 15th (2 weeks vote period). > > We can then put out a news on the Cam

Re: [DISCUSS] - New Apache Camel Logo - Move on with the procedure

2017-04-10 Thread Claus Ibsen
Hi Thanks for picking up this Zoran. The google form look good to me. However I do think the voting period is too narrow, and doing this on the same time as we are release 2.19.0 takes away our focus. On top of this there is also the easter holidays this month. I suggest to put the word about a