Re: Wiki Access

2016-03-21 Thread Anbu
Hi Claus, I have updated the Camel-Kafka component Wiki page and please find the JIRA#CAMEL-9734. Thanks! Anbu -- View this message in context: http://camel.465427.n5.nabble.com/Wiki-Access-tp5779327p5779458.html Sent from the Camel Development mailing list archive at Nabble.com.

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Claus Ibsen
Hi Gregor Ah yeah sorry for missing that, yeah it was just to pass in the CamelContext to the created type converter registry as its needed. On Mon, Mar 21, 2016 at 10:54 PM, Gregor Zurowski wrote: > Hi Claus, > > I applied the previously described change to OsgiSpringCamelContext > (see > http

Camel.2.17.x.notest - Build # 1 - Failure

2016-03-21 Thread Apache Jenkins Server
The Apache Jenkins build system has built Camel.2.17.x.notest (build #1) Status: Failure Check console output at https://builds.apache.org/job/Camel.2.17.x.notest/1/ to view the results.

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Gregor Zurowski
Hi Claus, I applied the previously described change to OsgiSpringCamelContext (see https://github.com/apache/camel/commit/1d3c090b37e61d46cf058fa5052227a64de20845) to branches master and 2.17.x. I am currently building a new RC for 2.17.0. Thanks, Gregor On Mon, Mar 21, 2016 at 10:20 PM, Grego

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Gregor Zurowski
Christian, thanks a lot for settings this up. Could you briefly describe the steps involved with this, so we can add it to the release guide? Thanks, Gregor On Mon, Mar 21, 2016 at 10:12 PM, Christian Müller wrote: > Jenkins jobs are set up and scheduled. > > Best, > Christian > ---

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Gregor Zurowski
Hi Claus, I believe the issue can be fixed by changing the invocation of the OsgiTypeConverter constructor on line 48 of class OsgiSpringCamelContext from: return new OsgiTypeConverter(ctx, getInjector(), finder); to: return new OsgiTypeConverter(ctx, this, getInjector(), finder); Please let m

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Christian Müller
https://builds.apache.org/view/A-D/view/Camel/ Christian - Software Integration Specialist Apache Member V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer Apache Incubator PMC Member https://www.linkedin.com/pub/christian-mueller/11/551/642 On Mon, Mar 21, 20

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Christian Müller
Jenkins jobs are set up and scheduled. Best, Christian - Software Integration Specialist Apache Member V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer Apache Incubator PMC Member https://www.linkedin.com/pub/christian-mueller/11/551/642 On Mon, Mar 21, 2016

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Gregor Zurowski
Hi Claus, It seems that the recent commit for CAMEL-9730 broke the OsgiSpringCamelContext class of the camel-spring module on branch-2.17.x: === [...] [INFO] [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ camel-spring --- [INFO] [INFO] Changes detected - recompiling the module

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Claus Ibsen
On Mon, Mar 21, 2016 at 4:33 PM, Claus Ibsen wrote: > On Mon, Mar 21, 2016 at 3:26 PM, Gregor Zurowski > wrote: >> @Claus: Do we want to include the following commit in 2.17.0 as well? >> >> https://github.com/apache/camel/commit/d48cfeef1aa7a4760a3c43533a558de8f6a8cff9 >> > > Yes that is a good

[VOTE] [CANCEL] Release Apache Camel 2.17.0

2016-03-21 Thread Gregor Zurowski
As previously discussed in this thread, this vote is cancelled due to a NPE in camel-jaxb when used with CamelTestBlueprint. The bug has been fixed [1] and a new release candidate will be created. Thanks, Gregor [1] https://github.com/apache/camel/commit/e718b6711b56996766cd2f803f2dcb313b510587

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Claus Ibsen
On Mon, Mar 21, 2016 at 3:26 PM, Gregor Zurowski wrote: > @Claus: Do we want to include the following commit in 2.17.0 as well? > > https://github.com/apache/camel/commit/d48cfeef1aa7a4760a3c43533a558de8f6a8cff9 > Yes that is a good one to get in, you are welcome to merge it. > Thanks, > Gregor

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Gregor Zurowski
@Claus: Do we want to include the following commit in 2.17.0 as well? https://github.com/apache/camel/commit/d48cfeef1aa7a4760a3c43533a558de8f6a8cff9 Thanks, Gregor On Mon, Mar 21, 2016 at 2:35 PM, Claus Ibsen wrote: > And btw this does not mean people should stop testing the current RC. > We w

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Andrea Cosentino
Claus already backported on 2.17.x branch. He was too fast :-) -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Monday, March 21, 2016 2:38 PM, And

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Andrea Cosentino
Hi Gregor, Yes, thank you. This commit is a minor one: https://github.com/apache/camel/commit/a4ebd77174d43f0e23792dc03fd88530db8a29ed Thanks! -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@y

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Gregor Zurowski
Hi Claus, Thanks for your feedback. I will merge your OSGi fix into the 2.17.x branch tonight and roll another RC. Any other commits that should be included in 2.17.0 that were committed on the master branch in the meantime? Thanks, Gregor On Mon, Mar 21, 2016 at 2:25 PM, Claus Ibsen wrote:

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Claus Ibsen
And btw this does not mean people should stop testing the current RC. We want as much feedback as possible. On Mon, Mar 21, 2016 at 2:34 PM, Claus Ibsen wrote: > Hi > > Okay its fixed now and pushed to master branch. > > I think it will cause problems for karaf users so I am voting a -1 so > we

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Claus Ibsen
Hi Okay its fixed now and pushed to master branch. I think it will cause problems for karaf users so I am voting a -1 so we can re-cut a RC. Gregor, can you re-cut from the master branch to pickup this fix and a few other minor ones? On Mon, Mar 21, 2016 at 1:37 PM, Claus Ibsen wrote: > Hi >

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Claus Ibsen
On Mon, Mar 21, 2016 at 2:18 PM, Grzegorz Grzybek wrote: > hmm, *could be* related to https://issues.apache.org/jira/browse/SM-2772, > I'll check it. > No it was in Camel itself in some of its osgi modules. I have fixed it. > regards > Grzegorz > > 2016-03-21 13:37 GMT+01:00 Claus Ibsen : > >> H

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Grzegorz Grzybek
hmm, *could be* related to https://issues.apache.org/jira/browse/SM-2772, I'll check it. regards Grzegorz 2016-03-21 13:37 GMT+01:00 Claus Ibsen : > Hi > > I found a NPE bug when using osgi blueprint testing with camel-jaxb > https://issues.apache.org/jira/browse/CAMEL-9730 > > And could likely

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Claus Ibsen
Hi I found a NPE bug when using osgi blueprint testing with camel-jaxb https://issues.apache.org/jira/browse/CAMEL-9730 And could likely also be a problem when running in real karaf. On Mon, Mar 21, 2016 at 9:52 AM, Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Gerard Klijs
+1 using the staging repo the poc with secure kafka connection works. On Mon, Mar 21, 2016 at 12:32 PM johndament wrote: > Actually, nevermind on the dependencies part. The only 3P libs being > shipped > are slf4j and jasypt (btw, do those have to be shipped?) > > > > -- > View this message in

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread johndament
Actually, nevermind on the dependencies part. The only 3P libs being shipped are slf4j and jasypt (btw, do those have to be shipped?) -- View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-17-0-tp5779375p5779383.html Sent from the Camel Development maili

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread johndament
I noticed that your NOTICE file says to find the LICENSE.txt in the licenses directory. There is no licenses directory and the file is found at the root of the archive. In addition, a number of your dependencies are not apache v2 licensed. I'm not sure that I see the proper level of attribution

Re: [VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Thomas Diesler
+1 from wildfly-camel > On 21 Mar 2016, at 09:52, Gregor Zurowski wrote: > > Hi Everyone: > > This is a vote to release Apache Camel 2.17.0, a new minor version > with ~450 improvements, fixes and new features. > > Release notes: > https://iss

[VOTE] Release Apache Camel 2.17.0

2016-03-21 Thread Gregor Zurowski
Hi Everyone: This is a vote to release Apache Camel 2.17.0, a new minor version with ~450 improvements, fixes and new features. Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=1268 Staging repository: https://repository.apache.org/content/rep

Re: Camel 2.17.0 Release

2016-03-21 Thread Gregor Zurowski
Hi, I have closed the staging repository and will send out the vote in a minute. I will update the release guide (http://camel.apache.org/release-guide.html) with additional instructions on how to create minor versions over the next few days. Also, if you want me to point out specific 2.17.0 cha

Re: Camel 2.17.0 Release

2016-03-21 Thread Antonin Stefanutti
Awesome, thanks Gregor! > On 21 Mar 2016, at 09:10, Claus Ibsen wrote: > > Hi > > Yay that sounds great. Good to hear the 2.17 is on the way. > > On Mon, Mar 21, 2016 at 9:06 AM, Gregor Zurowski > wrote: >> Hi Everyone: >> >> I have created the RC and will make it available shorty. I will a

[GitHub] camel pull request: [CAMEL-9716] Feature/kafka seek support

2016-03-21 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/camel/pull/910 --- 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 enabl

Re: Camel 2.17.0 Release

2016-03-21 Thread Claus Ibsen
Hi Yay that sounds great. Good to hear the 2.17 is on the way. On Mon, Mar 21, 2016 at 9:06 AM, Gregor Zurowski wrote: > Hi Everyone: > > I have created the RC and will make it available shorty. I will also > update the master branch to start development of version > 2.18-SNAPSHOT. > > Thanks,

Re: Camel 2.17.0 Release

2016-03-21 Thread Gregor Zurowski
Hi Everyone: I have created the RC and will make it available shorty. I will also update the master branch to start development of version 2.18-SNAPSHOT. Thanks, Gregor On Sun, Mar 20, 2016 at 9:18 PM, Gregor Zurowski wrote: > Hi Everyone: > > I have verified the code on the master branch and

Re: Camel 2.17.0 Release

2016-03-21 Thread Andrea Cosentino
Thanks Gregor :-) -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Sunday, March 20, 2016 9:19 PM, Gregor Zurowski wrote: Hi Everyone: I have ver