Re: Closing Down for Apache Camel 2.17.0 Release

Its responsible for shutting down routes in a graceful manner. The other resources will still be handled by CamelContext to shutdown. This leaves the problem at hand with properly shutting down all the routes in a reliable manner to the ShutdownStrategy. View more : http://ketsatgiadinh.vn/

Re: Closing Down for Apache Camel 2.17.0 Release

Hi Gregor I think the current code is ready for a cutting a RC. The karaf features has been improved and fixed and they now install nicely in karaf containers. Do you have time to cut the RC this weekend? On Sun, Mar 13, 2016 at 11:35 AM, Gregor Zurowski wrote: > Hi Claus, > > Sure, we should

Re: Closing Down for Apache Camel 2.17.0 Release

Hi Claus, Thanks for your update. I will start building the release candidate tomorrow. Thanks, Gregor On Fri, Mar 18, 2016 at 11:09 AM, Claus Ibsen wrote: > Hi Gregor > > I think the current code is ready for a cutting a RC. > > The karaf features has been improved and fixed and they now ins

Re: Closing Down for Apache Camel 2.17.0 Release

Hi Okay fixed a compile issue on java 1.7, and did the RAT check which passed. The code should be ready. On Fri, Mar 18, 2016 at 11:09 AM, Claus Ibsen wrote: > Hi Gregor > > I think the current code is ready for a cutting a RC. > > The karaf features has been improved and fixed and they now inst

Re: Closing Down for Apache Camel 2.17.0 Release

Hi Gregor, If want to build a RC release of Camel 2.17.x, you can just create a new branch of camel-2.17.x and run maven release on that branch, or just cut a Camel 2.17.0 from the master branch, then create camel-2.17.x branch from the RC tag. You need update the pom version in the master branch

Re: Closing Down for Apache Camel 2.17.0 Release

Hi Claus, Sure, we should definitely wait for feedback on your recent Karaf-related changes. In the meantime I will get in touch with Christian, Willem, Dan or Hadrian to get some more details about cutting minor releases. I will update the docs once I tested the necessary steps. Thanks, Gregor

Re: Closing Down for Apache Camel 2.17.0 Release

I guess is a good idea to give the possibility to Karaf users to test the snapshot. -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Sunday, March 13, 2016 8:53 AM, Claus Ib

Re: Closing Down for Apache Camel 2.17.0 Release

On Sat, Mar 12, 2016 at 12:44 PM, Gregor Zurowski wrote: > Hi Claus, > > Not a problem, just let me know once you are done with your changes. > I planned to cut the release tomorrow. > I wonder if we should give the Karaf users a chance to try the SNAPSHOT changes on their karaf servers. And mayb

Re: Closing Down for Apache Camel 2.17.0 Release

Hi Claus, Not a problem, just let me know once you are done with your changes. I planned to cut the release tomorrow. I also realized that the release guide describes the minor release branching process for SVN, not Git. I assume I will need to perform the following: - Create a new branch-2.17.

Re: Closing Down for Apache Camel 2.17.0 Release

Hi Gregor, I am currently working on some osgi fixes to make Camel installing on karaf 2.4, 3 and 4. And as well fixing an issue with http servlet being imported as 3.1+ and not 3.0+. Otherwise it wont work on older karaf versions either. On Fri, Mar 11, 2016 at 9:16 AM, Claus Ibsen wrote: > Hi

Re: Closing Down for Apache Camel 2.17.0 Release

Hi Gregor Yeah sound good. I think a good time is this weekend if you have the time. If not then early next week. I am currently checking checkstyle and license headers and whatnot to help make sure the source code is ready for you. On Thu, Mar 10, 2016 at 8:53 PM, Gregor Zurowski wrote: > Hi

Re: Closing Down for Apache Camel 2.17.0 Release

Hi Claus, Sure, I can cut the RC. When do you think is a good time? This weekend or some time next week? Thanks, Gregor On Thu, Mar 10, 2016 at 10:46 AM, Claus Ibsen wrote: > Hi > > Its been long enough. We should get started on cutting a RC. > > I wonder if anyone who are familiar with doin

Re: Closing Down for Apache Camel 2.17.0 Release

Hi Its been long enough. We should get started on cutting a RC. I wonder if anyone who are familiar with doing release have time and would like to cut the RC? Maybe Gregor Z? On Thu, Feb 18, 2016 at 10:56 AM, Claus Ibsen wrote: > Hi > > Its been a while since Camel 2.16.0 was released > http

Re: Closing Down for Apache Camel 2.17.0 Release

Hi The camel-kafka to java migration is now done, and we are getting much closer. After the 2.17.0 release we should IMHO get a new round of patch releases out so we can do 2.16.3 and the last release of 2.15.x. On Fri, Mar 4, 2016 at 6:52 PM, Antonin Stefanutti wrote: > I’ve just pushed a firs

Re: Closing Down for Apache Camel 2.17.0 Release

I’ve just pushed a first spike of the camel-test-cdi module. I’ll continue working on it and documenting it but that first version is good to go for the 2.17.0 release. Antonin > On 04 Mar 2016, at 17:17, Claus Ibsen wrote: > > Hi > > Yeah sure, but we are likely taking up next week or a bit

Re: Closing Down for Apache Camel 2.17.0 Release

I could really use some help with https://issues.apache.org/jira/browse/CAMEL-9570 - I’m stuck. I’ve been working on it all week and haven’t made any progress. I’d really like to be able to get this in 2.17.0 - it’s a real problem for my dep

Re: Closing Down for Apache Camel 2.17.0 Release

Hi Yeah sure, but we are likely taking up next week or a bit longer to finish up the other stuff. But sure any start of a test module for cdi is better than nothing. On Fri, Mar 4, 2016 at 5:13 PM, Antonin Stefanutti wrote: > Hi Claus, > > I’ve been working on a camel-test-cdi module lately. It’

Re: Closing Down for Apache Camel 2.17.0 Release

Hi Claus, I’ve been working on a camel-test-cdi module lately. It’s not full-fledge as I want it to be yet, though I have a working thing that’d be a great addition to the new Camel CDI component. I can polish up what I have quickly so that it’s part of 2.17.0 and complete the work afterward.

Re: Closing Down for Apache Camel 2.17.0 Release

Hi There has a been a bunch of new components and data formats etc. That is all lovely. But we should start to close down for real and fix the remainder bugs and whatnot. There is still that camel-kafka as just java upgrade that would be great to get in. I just fixed all the CS rules. The builds

Re: Closing Down for Apache Camel 2.17.0 Release

Hi CamelBlueprintTestSupport now provides new setConfigAdminInitialConfiguration(Properties) method that acts just like loadConfigAdminConfigurationFile(), but doesn't force user to provide property files. Properties may be specified in test class itself. I'll describe this in wiki. regards Grzeg

Re: Closing Down for Apache Camel 2.17.0 Release

amel now supports a pluggable shutdown strategy using org.apache.camel.spi.ShutdownStrategy. Its responsible for shutting down routes in a graceful manner. The other resources will still be handled by CamelContext to shutdown. This leaves the problem at hand with properly shutting down all the rout

Re: Closing Down for Apache Camel 2.17.0 Release

Hi Claus, Camel-nats is already finished. I just need to add docs in confluence. In the future we have to switch from java_nats (deprecated) to jnats. For the moment the component is ok and ready to be released. -- Andrea Cosentino -- Apache Camel PMC Member Ap

Re: Closing Down for Apache Camel 2.17.0 Release

Hi We start to look better now. The CI server last build passed all tests https://builds.apache.org/job/Camel.trunk.fulltest.java8/ There is a camel-nats and camel-hysterix component in the works, but we should likely push them for next release unless they are ready really soon. I would love to

Closing Down for Apache Camel 2.17.0 Release

Hi Its been a while since Camel 2.16.0 was released http://camel.apache.org/2015/10/09/apache-camel-2160-released.html I think we should start to close down for a 2.17 release, so we can get a release out, maybe within the first couple of weeks in March? Any thoughts? The CI servers seems pret