[VOTE] Camel 2.16.0 (attempt 2)

This is a vote to release Apache Camel 2.16.0. There was a TON of work done over the last 6 months to get this ready so it’s time to get it out. Tag: https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=cad9dc2be555b7460e141fde586ac2edf09159c5 Staging area: https://repository.apache.o

[CANCEL] [VOTE] Camel 2.16.0

Will respin this shortly once i get everything cleaned up. Dan > On Sep 29, 2015, at 9:25 PM, Daniel Kulp wrote: > > This is a vote to release Apache Camel 2.16.0. There was a TON of work done > over the last 6 months to get this ready so it’s time to get it out. > > Tag: > https://git-w

Re: Update on camel-extra

The component has to be built by the user, it doesn't ship the IBM MQ jar. The dependencies specified in the pom have to be present in the user local repo (installed using mvn install:install-file command). So, the codebase is OK (it's already used in production), but the build has to be done

Re: Update on camel-extra

And here is a third IBM one (the CICS component): https://github.com/camel-extra/camel-extra/pull/10 Unsure how we should go about the library issue. We definitively cannot upload it to central, but might set the scope to provided and so some pre-build hack to download and install it for building:

Re: Update on camel-extra

Hi Yeah it would be good to get camel-extra back on track. Hopefully at the github home. That said your components uses IBM. There was another talk for some other camel-extra IBM component. http://camel.465427.n5.nabble.com/Camel-WXS-component-tp5772096.html I would like to know more about the i

Update on camel-extra

Hi all, I worked on a Camel component which works natively with IBM WebSphere MQ. For obvious license reason, this component can be directly in the ASF codebase. So, I propose to donate it into camel-extra: https://github.com/camel-extra/camel-extra Related to that, I would like to do some

Re: [VOTE] Camel 2.16.0

+1 (binding) Regards JB On 09/30/2015 03:25 AM, Daniel Kulp wrote: This is a vote to release Apache Camel 2.16.0. There was a TON of work done over the last 6 months to get this ready so it’s time to get it out. Tag: https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=a9ddbc94874817

Re: [VOTE] Camel 2.16.0

Hi Okay the PR has been merged. The branch should be ready for a new RC. On Mon, Oct 5, 2015 at 12:24 PM, Claus Ibsen wrote: > Hi Dan > > I am just merging in this PR > https://issues.apache.org/jira/browse/CAMEL-9189 > > When that work is done then I think we are ready for a new RC > > On Sun,

Re: [VOTE] Camel 2.16.0

Confirmed. I've only upgraded gson yesterday, now I stop activities on Camel for the new RC :-) Thanks Dan. Andrea Cosentino - Apache Camel PMC Member & Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Monday, October 5, 2015 12:2

Re: [VOTE] Camel 2.16.0

Hi Dan I am just merging in this PR https://issues.apache.org/jira/browse/CAMEL-9189 When that work is done then I think we are ready for a new RC On Sun, Oct 4, 2015 at 4:38 AM, Daniel Kulp wrote: > I can respin the release on Monday. > > Dan > > >> On Oct 3, 2015, at 3:52 AM, Claus Ibsen wro

Re: [VOTE] Camel 2.16.0

@arnaudeprez can you provide output of `mvn dependency:tree` in your project? regards Grzegorz 2015-10-05 9:10 GMT+02:00 arnaudeprez : > Thx for your answer. > > I actually don't use aries dependencies directly, I count on camel-blueprint > & camel-test-blueprint to bring me what is needed. It w

Camel.2.15.x.notest - Build # 145 - Failure

The Apache Jenkins build system has built Camel.2.15.x.notest (build #145) Status: Failure Check console output at https://builds.apache.org/job/Camel.2.15.x.notest/145/ to view the results.

Re: [VOTE] Camel 2.16.0

Thx for your answer. I actually don't use aries dependencies directly, I count on camel-blueprint & camel-test-blueprint to bring me what is needed. It would be nice to upgrade blueprint dependencies in camel-test & camel-test-blueprint. Rgds, -- View this message in context: http://camel.465