Re: Getting ready for Apache Camel 2.18 Release

2016-10-05 Thread Gregor Zurowski
I was finally able to complete the process without issues, as well as closing the artifact repository without any errors. I will send out the vote for 2.18.0 shortly. Thanks, Gregor On Tue, Oct 4, 2016 at 9:58 PM, Gregor Zurowski wrote: > Hi Everyone: > >

Re: Getting ready for Apache Camel 2.18 Release

2016-10-04 Thread Gregor Zurowski
Hi Everyone: Unfortunately, closing the staging repository did not succeed and was aborted with the following error message: "Missing MD5: '/org/apache/camel/camel-optaplanner-starter/2.18.0/camel-optaplanner-starter-2.18.0.pom.md5'" It seems that something went wrong during the upload to

Re: Getting ready for Apache Camel 2.18 Release

2016-10-04 Thread Gregor Zurowski
Hi Everyone: I was finally able to create the release without any timeout errors and I am currently closing the staging repository. I will send out the vote for the release candidate shortly. Thanks, Gregor On Tue, Oct 4, 2016 at 9:03 AM, Gregor Zurowski wrote: > Hi

Re: Getting ready for Apache Camel 2.18 Release

2016-10-04 Thread Gregor Zurowski
Hi Everyone: Unfortunately the second attempt to release the 2.18.0 RC failed close towards the end of the build process due to connectivity issues with the Apache repository server. I have just started the release process once again and will post updates to this thread. Thanks, Gregor On

Re: Getting ready for Apache Camel 2.18 Release

2016-10-01 Thread Claus Ibsen
The job completed and there was 2 flaky tests about camel-quartz (deprecated) which can happen from time to time. We are looking good for cutting the RC. On Sat, Oct 1, 2016 at 1:32 PM, Claus Ibsen wrote: > Hi > > The previous CI job was aborted after 5h30m because it

Re: Getting ready for Apache Camel 2.18 Release

2016-10-01 Thread Claus Ibsen
Hi The previous CI job was aborted after 5h30m because it was configured to timeout after that duration, but it was still going, it was running the itests at the time. So I have bumped up the timeout value and kicked off a new one

Re: Getting ready for Apache Camel 2.18 Release

2016-09-30 Thread Claus Ibsen
Hi I kicked off a CI test https://builds.apache.org/view/A-D/view/Camel/job/Camel.trunk.fulltest.java8/965/ The CI server had a bit of issues of late with weird hudson/jenkins errors and some of them dont have so much memory, so they can't run the full test suite. Lets keep an eye on this one,

Re: Getting ready for Apache Camel 2.18 Release

2016-09-30 Thread Andrea Cosentino
I finished the alignment. I guess we are ready to cut the release. Thoughts? Last minute addition? :-) -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd

Re: Getting ready for Apache Camel 2.18 Release

2016-09-29 Thread Andrea Cosentino
And obviously, thanks Gregor! -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Thursday, September 29, 2016 4:59 PM, Andrea Cosentino

Re: Getting ready for Apache Camel 2.18 Release

2016-09-29 Thread Andrea Cosentino
I'll try to align everything during tomorrow. So I guess It will be ok. -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Thursday, September 29,

Re: Getting ready for Apache Camel 2.18 Release

2016-09-29 Thread Gregor Zurowski
Hi Claus, I will be able to create a release candidate for 2.18 this weekend, so we could start the vote around Sunday/Monday. Does that work for everyone? Thanks, Gregor On Thu, Sep 29, 2016 at 3:17 PM, Claus Ibsen wrote: > Hi Gregor > > When Andreas have updated the

Re: Getting ready for Apache Camel 2.18 Release

2016-09-29 Thread Claus Ibsen
Hi Gregor When Andreas have updated the SMX bundles tomorrow, then we should be ready to start cutting a RC. I wonder when you have time in your calendar to cut a release? On Wed, Sep 28, 2016 at 9:18 AM, Andrea Cosentino wrote: > Hello Claus, > > We are on

Re: Getting ready for Apache Camel 2.18 Release

2016-09-28 Thread Andrea Cosentino
Hello Claus, We are on vote now. Hopefully we should be able to have the bundles on Friday. -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On

Re: Getting ready for Apache Camel 2.18 Release

2016-09-28 Thread Claus Ibsen
Hi Andrea How is it going with the SMX bundle release? On Fri, Sep 23, 2016 at 4:43 PM, Andrea Cosentino wrote: > During the weekend JB will cut release for SMX bundles. > > So we should be able to align karaf features and be ready to release by the > middle of

Re: Getting ready for Apache Camel 2.18 Release

2016-09-28 Thread fabryprog
for this problem open this issue: https://issues.apache.org/jira/browse/CAMEL-10349 -- View this message in context: http://camel.465427.n5.nabble.com/Getting-ready-for-Apache-Camel-2-18-Release-tp5786942p5788128.html Sent from the Camel Development mailing list archive at Nabble.com.

Re: Getting ready for Apache Camel 2.18 Release

2016-09-27 Thread fabryprog
Hello, I may have found a bug derived from 2.18 Before 2.18, i can specified an header like: [{"firstField": "firstValue", "secondField":"secondValue"}] In my bean, *myHeader* will be cast to *ArrayList>* After 2.18 upgrade i had an error

Re: Getting ready for Apache Camel 2.18 Release

2016-09-23 Thread Andrea Cosentino
During the weekend JB will cut release for SMX bundles. So we should be able to align karaf features and be ready to release by the middle of the next week. -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email:

Re: Getting ready for Apache Camel 2.18 Release

2016-09-22 Thread Andrea Cosentino
I physically removed the folders of the starters and I pulled master aligning to the codebase. This way it should work fine. -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter:

Re: Getting ready for Apache Camel 2.18 Release

2016-09-22 Thread Nicola Ferraro
That Happened also to Andrea yesterday. The cause should be the blacklist, that is hardcoded in the camel-package maven plugin, so you have to rebuild the plugin first. The plugin does not delete the starters, it is just able to create them. They have been deleted from the repo, but probably some

Re: Getting ready for Apache Camel 2.18 Release

2016-09-22 Thread Claus Ibsen
Hi Nicola When I build the latest code then some -starter modules are generated for modules that ought to be blacklisted components-starter/camel-ejb-starter/ components-starter/camel-ibatis-starter/ components-starter/camel-jclouds-starter/ components-starter/camel-quartz-starter/ On Fri, Sep

Re: Getting ready for Apache Camel 2.18 Release

2016-09-22 Thread Claus Ibsen
Hi Jean Thanks let us know how the SMX bundles release are going, so Andreas can update the karaf features and run the tests to ensure the upgrades work for us. On Wed, Sep 21, 2016 at 12:44 PM, Jean-Baptiste Onofré wrote: > Hi guys > > I'm starting the SMX bundles release

Re: Getting ready for Apache Camel 2.18 Release

2016-09-21 Thread Jean-Baptiste Onofré
Hi guys I'm starting the SMX bundles release now. Regards JB On Sep 21, 2016, 03:34, at 03:34, Andrea Cosentino wrote: >Not sure, it depends from Jean Baptiste Onofrè. > -- >Andrea Cosentino >-- >Apache Camel PMC Member >Apache

Re: Getting ready for Apache Camel 2.18 Release

2016-09-21 Thread Andrea Cosentino
Not sure, it depends from Jean Baptiste Onofrè. -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Wednesday, September 21, 2016 12:17 PM, Claus

Re: Getting ready for Apache Camel 2.18 Release

2016-09-21 Thread Claus Ibsen
Can you speedup those SMX bundle release. We dont want to hold back Camel release. There is people eager waiting for the 2.18.0 release of Camel. On Wed, Sep 21, 2016 at 11:51 AM, Andrea Cosentino wrote: > Maybe we should wait for the next SM bundles release. > >

Re: Getting ready for Apache Camel 2.18 Release

2016-09-21 Thread Luca Burgazzoli
Hi Claus, upgrade to Saxon 9.7 will be merged today. Luca --- Luca Burgazzoli On Wed, Sep 21, 2016 at 11:31 AM, Claus Ibsen wrote: > Hi > > Just a quick update. > > Nicola has now merged his great work on making Camel and Spring Boot > work well together with a

Re: Getting ready for Apache Camel 2.18 Release

2016-09-21 Thread Claus Ibsen
Hi Just a quick update. Nicola has now merged his great work on making Camel and Spring Boot work well together with a curated list of -starter components that works. There is another Camel SB ticket merged about nested configuration which we need a bit time to improved/fix etc. And also

Re: Getting ready for Apache Camel 2.18 Release

2016-09-16 Thread Nicola Ferraro
Hi Claus, I started working on that this morning. I think I'll provide the new BOM and related updates early next week. On Fri, Sep 16, 2016 at 9:38 AM, Claus Ibsen wrote: > Hi Nicola > > How does your calendar look like? I wonder if you have time to work > more on

Re: Getting ready for Apache Camel 2.18 Release

2016-09-16 Thread Claus Ibsen
Hi Nicola How does your calendar look like? I wonder if you have time to work more on this Camel and Spring Boot stuff? I am afraid this one is the major task we have left before we can get started on the Camel 2.18 release and IMHO first class Spring Boot support is a major win/goal for Camel.

Re: Getting ready for Apache Camel 2.18 Release

2016-09-15 Thread Claus Ibsen
On Wed, Sep 14, 2016 at 3:32 PM, Nicola Ferraro wrote: > Well, it was one of the drawbacks of the approach. Forcing users to include > *only* the camel BOM allows us to completely control the dependencies, but > it's probably a too strict requirement for users. > > We can

Re: Getting ready for Apache Camel 2.18 Release

2016-09-14 Thread Nicola Ferraro
Well, it was one of the drawbacks of the approach. Forcing users to include *only* the camel BOM allows us to completely control the dependencies, but it's probably a too strict requirement for users. We can also provide a option 1+2: i.e. a auto-generated Camel BOM without any conflict with the

Re: Getting ready for Apache Camel 2.18 Release

2016-09-12 Thread Nicola Ferraro
I've worked on the spring-boot starters and BOM topic and opened a PR recently. You can find a summary here [ https://issues.apache.org/jira/browse/CAMEL-10222] and this is latest PR: https://github.com/apache/camel/pull/1164. Basically, the aim is allowing users to add camel components to their

Re: Getting ready for Apache Camel 2.18 Release

2016-09-09 Thread Quinn Stevenson
Thanks for taking a look at the PR Thomas - I really appreciate the feedback. 1) The parent pom was wrong because I created this PR before the change from 2.18-SNAPSHOT to 2.18.0-SNAPSHOT took place - it’s been out there a while 2) My bad on the READMEmd - you can probably tell where I copied

Re: Getting ready for Apache Camel 2.18 Release

2016-09-09 Thread Andrea Cosentino
The docs now are completed. The last four languages were added. -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Sunday, August 28, 2016 11:29 AM,

Re: Getting ready for Apache Camel 2.18 Release

2016-09-08 Thread Walzer, Thomas
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: Getting ready for Apache Camel 2.18 Release

2016-09-06 Thread Claus Ibsen
Hi I added to our maven tool that it can fail the build if our component docs has problems. You can set this value to true https://github.com/apache/camel/blob/master/components/pom.xml#L286 And then do a mvn clean install -Dtest=false in the components directory. There seems to be a bunch of

Re: Getting ready for Apache Camel 2.18 Release

2016-09-06 Thread Andrea Cosentino
For the docs, I should be able to complete the languages this week. :-) -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Tuesday, September 6,

Re: Getting ready for Apache Camel 2.18 Release

2016-09-06 Thread Claus Ibsen
On Sun, Aug 28, 2016 at 11:28 AM, Claus Ibsen wrote: > Hi > > Hope everybody had good summer vacation. I had my vacation in parts > and have next week as PTO. > > We should get started to close down on the upcoming Camel 2.18 release. > > > There is some outstanding work

Re: Getting ready for Apache Camel 2.18 Release

2016-09-02 Thread Quinn Stevenson
I’ve had a pull-request out there for a while (https://github.com/apache/camel/pull/987 ) - looking for some feedback on the example project that attempts to show how to use camel-test-karaf. I could really use some input. I think fleshing-out this

Re: Getting ready for Apache Camel 2.18 Release

2016-08-30 Thread Luca Burgazzoli
Hi Claus, Yep, I'm going to close CAMEL-10274. --- Luca Burgazzoli On Tue, Aug 30, 2016 at 11:25 AM, Claus Ibsen wrote: > Hi Luca > > I can see you found out about the problem and found a solution. So the > examples should work again. > > On Mon, Aug 29, 2016 at 12:39

Re: Getting ready for Apache Camel 2.18 Release

2016-08-30 Thread Claus Ibsen
Hi Luca I can see you found out about the problem and found a solution. So the examples should work again. On Mon, Aug 29, 2016 at 12:39 PM, Luca Burgazzoli wrote: > Hi Claus, > > can you tell me something more about log4j2 vs jetty plugin ? > > --- > Luca Burgazzoli > >

Re: Getting ready for Apache Camel 2.18 Release

2016-08-29 Thread Luca Burgazzoli
Hi Claus, can you tell me something more about log4j2 vs jetty plugin ? --- Luca Burgazzoli On Sun, Aug 28, 2016 at 11:28 AM, Claus Ibsen wrote: > Hi > > Hope everybody had good summer vacation. I had my vacation in parts > and have next week as PTO. > > We should get