You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Gregor Zurowski <gr...@list.zurowski.org> on 2017/04/03 12:14:41 UTC

Re: Camel 2.19 Roadmap

Hi,

Are we getting closer to build a 2.19.0 release?  I would volunteer
for creating the release, just wanted to check when would be a good
time to do so.

Thanks,
Gregor


On Wed, Mar 15, 2017 at 9:29 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> Just wanted to bring up that we are closing in on a good time for
> doing a new release.
>
> For example in mid April it would be around 6 months since the last
> 2.18.0 release.
>
> Therefore we should start closing down and fixing bugs, and make sure
> the CI servers and tests are in good shape.
> This morning we have fixed a number of recent test failures and are
> down to only 1 test failure now.
>
>
>
> On Mon, Jan 16, 2017 at 10:28 AM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi
>>
>> There is a bunch of stuff which we can/should have on the roadmap to
>> complete for the Camel 2.19 release.
>>
>> Here is on top of my head
>>
>> 1)
>> Finish migrating the wiki documentation to adoc files. I think its
>> most of the EIP patterns that are missing. There is a basic list of
>> EIPs here: https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc
>>
>> 2)
>> Generate documentation and website. Maybe documentation first and then
>> we come up with a modern website later - when we have a new logo as
>> well.
>>
>> 3)
>> Mark more stuff to @deprecate so we dont drag them into Camel 3.0.
>> This is both components / and other artifacts.
>> And as well the camel-core APIs where there is maybe more we can deprecate.
>> For example the old stuff that was created prior to the component docs
>> we do now with the apt plugin at build time instead of this old code
>> with runtime that dont really pan out anyway.
>>
>> 4)
>> Move spring-boot starters into the platforms folder. There is a ticket
>> about this.
>>
>> 5)
>> More improvements to spring boot auto configuration. We have a bunch
>> of tickets on that.
>>
>> 6)
>> Look at the health check API and see if there is something we can get
>> started on.
>> Possible some API to integrate with spring boot actuators (when using
>> SB) and allow each component to provide their own checks so they can
>> be implemented ad-hoc. There is a ticket about this.
>>
>> 7)
>> Possible some more teaks to camel-catalog based on feedback from IDEA
>> plugin and the maven validate goal.
>>
>> 8)
>> That CDI JEE transaction PR on github.
>> Ideally we would have had a transaction API in camel-core and then one
>> impl for camel-spring, and then another for camel-cdi-jee. But that
>> may require too much work.
>>
>> 9)
>> Work on the Java 8 DSL such as get more community feedback, and then
>> resolve the TODOs with the documentation updates and look into other
>> areas where the API can benefit from Java 8 lambdas and whatnot. I
>> dont think we have a ticket about this.
>>
>> 10)
>> Karaf users may want to improve/finish up the camel-test-karaf module
>> so its more usable and end users can use it to test integration tests
>> with Camel and Karaf.
>>
>> 11)
>> Introduce Camel Connectors (more about this later)
>>
>>
>> Anything else?
>>
>>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

Thanks Gregor.

The 2.19.0 is on VOTE now.
http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-19-0-tp5798264.html

On Mon, Apr 24, 2017 at 9:23 PM, Gregor Zurowski
<gr...@list.zurowski.org> wrote:
> Hi Everyone:
>
> I am starting to cut the 2.19.0 RC now.
>
> Thanks,
> Gregor
>
>
> On Mon, Apr 24, 2017 at 7:00 PM, Luca Burgazzoli <lb...@gmail.com> wrote:
>> Hi Gregor,
>>
>> I've committed my fixes.
>>
>>
>>
>> ---
>> Luca Burgazzoli
>>
>>
>> On Mon, Apr 24, 2017 at 6:10 PM, Luca Burgazzoli <lb...@gmail.com> wrote:
>>> Hi Gregor,
>>>
>>> I'm running a local build to see if there is any blocking issue some
>>> JIRA I'd like to include [1][2][3], it should not take too much and
>>> I'll post here as son  as I have merged my work on master.
>>>
>>>
>>> [1] https://issues.apache.org/jira/browse/CAMEL-11190
>>> [2] https://issues.apache.org/jira/browse/CAMEL-11191
>>> [3] https://issues.apache.org/jira/browse/CAMEL-11192
>>>
>>>
>>> ---
>>> Luca Burgazzoli
>>>
>>>
>>> On Mon, Apr 24, 2017 at 11:11 AM, Gregor Zurowski
>>> <gr...@list.zurowski.org> wrote:
>>>> Hi Claus,
>>>>
>>>> Alright, I guess this is the best we can do for now.  I also agree on
>>>> removing the regular examples from the release.  I would actually also
>>>> move them into a separate artifact group.  Currently they use the
>>>> group ID org.apache.camel, so we could move them into
>>>> org.apache.camel.example or similar.
>>>>
>>>> I will re-cut the release candidate tonight.
>>>>
>>>> Thanks,
>>>> Gregor
>>>>
>>>>
>>>> On Mon, Apr 24, 2017 at 10:49 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>> Hi Gregor
>>>>>
>>>>> So we have now fixed this by turning of those connector examples as
>>>>> they should not be in the release.
>>>>>
>>>>> We will later re-organize this and see what to do if any of this is
>>>>> needed as releases JAR in maven central.
>>>>> You could consider the same for the regular examples, they should
>>>>> maybe not be released either to maven central.
>>>>> But its a talk for another day.
>>>>>
>>>>> The master branch should be ready for a re-cut of the release.
>>>>>
>>>>> Let us know when you are able to work on this again. Thanks a lot for
>>>>> helping with the releases.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Apr 24, 2017 at 10:22 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>> Hi Gregor
>>>>>>
>>>>>> Okay so the connector examples are not yet intended for release (if
>>>>>> they ever would be).
>>>>>> So I have skipped them.
>>>>>>
>>>>>> People can try them from the source code as they do with the other
>>>>>> examples. That works fine.
>>>>>>
>>>>>> For a release process we may also need to add some extra logic so the
>>>>>> SNAPSHOT versions in the json files etc are replaced as part of a
>>>>>> release build. AFAIR you need to run 2 x build, to make it updated,
>>>>>> which you can't usually.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Apr 23, 2017 at 10:25 PM, Gregor Zurowski
>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>> Hi Everyone:
>>>>>>>
>>>>>>> I have finally managed to resolve all memory-related and
>>>>>>> machine-related issues, but I am hitting another road block in the
>>>>>>> release process.  The process fails when the new connector examples
>>>>>>> are about to get pushed to the artifact repository:
>>>>>>>
>>>>>>> [INFO] [ERROR] Failed to execute goal
>>>>>>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
>>>>>>> (default-deploy) on project beverage-component: Failed to deploy
>>>>>>> artifacts: Could not transfer artifact
>>>>>>> org.foo:beverage-component:jar:2.19.0 from/to apache.releases.https
>>>>>>> (https://repository.apache.org/service/local/staging/deploy/maven2):
>>>>>>> Failed to transfer file:
>>>>>>> https://repository.apache.org/service/local/staging/deploy/maven2/org/foo/beverage-component/2.19.0/beverage-component-2.19.0.jar.
>>>>>>> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
>>>>>>>
>>>>>>> This is likely caused by the group ID "org.foo" that is used in these
>>>>>>> modules, which will not be accepted by the Apache artifact repository.
>>>>>>>
>>>>>>> I could easily change the group ID of these examples to something like
>>>>>>> "org.apache.camel.example.connector".  While attempting to change
>>>>>>> this, I realized that there are JSON files in the example directories
>>>>>>> that directly reference these artifacts, for example in
>>>>>>> /salesforce-upsert-contact-connector/src/main/resources/camel-connector.json:
>>>>>>>
>>>>>>>   "groupId" : "org.foo",
>>>>>>>   "artifactId" : "salesforce-upsert-contact-connector",
>>>>>>>   "version" : "2.19.0-SNAPSHOT"
>>>>>>>
>>>>>>> I can update the group ID here as well, but the release process is not
>>>>>>> prepared to handle any of these JSON files for updating the version
>>>>>>> elements, i.e. 2.19.0-SNAPSHOT should have been rewritten to 2.19.0
>>>>>>> within the release preparation step.
>>>>>>>
>>>>>>> Please let me know how to proceed here.  Once we resolve this, I will
>>>>>>> restart the release.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Gregor
>>>>>>>
>>>>>>>
>>>>>>> On Sat, Apr 22, 2017 at 3:00 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>> Hi Gregor
>>>>>>>>
>>>>>>>> Sorry for adding that CS error this morning. I guess the extra text in
>>>>>>>> that exception message may have caused the line to be too long?
>>>>>>>>
>>>>>>>> I noticed some Maven WARNs about some examples was a bit wrong with
>>>>>>>> bundle vs jar. So I aligned them and just pushed.
>>>>>>>> I will step away from the computer so you should have a quiet time to
>>>>>>>> work on the release.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sat, Apr 22, 2017 at 2:52 PM, Gregor Zurowski
>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>> Hi Claus,
>>>>>>>>>
>>>>>>>>> I am still working on the release, just found some CS issues.
>>>>>>>>>
>>>>>>>>> I am using a different box now, because the OOME problems were
>>>>>>>>> definitely caused by some issues with the machine I was using
>>>>>>>>> previously.
>>>>>>>>>
>>>>>>>>> Will keep you posted.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Gregor
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sat, Apr 22, 2017 at 11:02 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>> Hi
>>>>>>>>>>
>>>>>>>>>> Building the release candidate takes up a lot of memory and Gregor has
>>>>>>>>>> hit a OOME with 6gb.
>>>>>>>>>>
>>>>>>>>>> We are cleaning up a bit in the project to upgrade some of the maven
>>>>>>>>>> plugins to use newer versions and reduce some cruft in the assembly.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Sat, Apr 22, 2017 at 9:20 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>> Hi
>>>>>>>>>>>
>>>>>>>>>>> Looking at the CI tests then they all look good (blue/green)
>>>>>>>>>>> https://builds.apache.org/view/A-D/view/Camel/
>>>>>>>>>>>
>>>>>>>>>>> .. except for the spring-boot tests which had two tests for
>>>>>>>>>>> camel-core-xml and camel-spring-dm which does not make sense at all so
>>>>>>>>>>> I have removed them. This should make this job blue as well.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Sat, Apr 22, 2017 at 9:13 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>>> Hi Gregor
>>>>>>>>>>>>
>>>>>>>>>>>> I can see you committed some fixed last evening.
>>>>>>>>>>>>
>>>>>>>>>>>> Do you think that you found all the "bugs" in terms of building a
>>>>>>>>>>>> release candidate, or do we have more problems?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Apr 21, 2017 at 9:22 PM, Gregor Zurowski
>>>>>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>>>>>> Hi Claus,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks for taking care of this.  I will start building the release
>>>>>>>>>>>>> candidate now.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Gregor
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Apr 21, 2017 at 9:11 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>>>>> Hi
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have just pushed fixes for RAT license check and CS checkstyle. They
>>>>>>>>>>>>>> all pass now.
>>>>>>>>>>>>>> I also added a few missing JARs in the release kit (the big
>>>>>>>>>>>>>> zip/tarball with all the JARs)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
>>>>>>>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>>>>>>>> Hi Everyone,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> That is great to hear, I will create the release candidate over the
>>>>>>>>>>>>>>> weekend, if all fixes are available on the master branch.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>> Gregor
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart <zo...@regvart.com> wrote:
>>>>>>>>>>>>>>>> Hi Cameleers,
>>>>>>>>>>>>>>>> Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> thank you :)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> zoran
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>>>>>>>> And Zoran has CAMEL-11181 outstanding.
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Zoran Regvart
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Claus Ibsen
>>>>>>>>>>>>>> -----------------
>>>>>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Claus Ibsen
>>>>>>>>>>>> -----------------
>>>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Claus Ibsen
>>>>>>>>>>> -----------------
>>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Claus Ibsen
>>>>>>>>>> -----------------
>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Claus Ibsen
>>>>>>>> -----------------
>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> http://davsclaus.com @davsclaus
>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Gregor Zurowski <gr...@list.zurowski.org>.
Hi Everyone:

I am starting to cut the 2.19.0 RC now.

Thanks,
Gregor


On Mon, Apr 24, 2017 at 7:00 PM, Luca Burgazzoli <lb...@gmail.com> wrote:
> Hi Gregor,
>
> I've committed my fixes.
>
>
>
> ---
> Luca Burgazzoli
>
>
> On Mon, Apr 24, 2017 at 6:10 PM, Luca Burgazzoli <lb...@gmail.com> wrote:
>> Hi Gregor,
>>
>> I'm running a local build to see if there is any blocking issue some
>> JIRA I'd like to include [1][2][3], it should not take too much and
>> I'll post here as son  as I have merged my work on master.
>>
>>
>> [1] https://issues.apache.org/jira/browse/CAMEL-11190
>> [2] https://issues.apache.org/jira/browse/CAMEL-11191
>> [3] https://issues.apache.org/jira/browse/CAMEL-11192
>>
>>
>> ---
>> Luca Burgazzoli
>>
>>
>> On Mon, Apr 24, 2017 at 11:11 AM, Gregor Zurowski
>> <gr...@list.zurowski.org> wrote:
>>> Hi Claus,
>>>
>>> Alright, I guess this is the best we can do for now.  I also agree on
>>> removing the regular examples from the release.  I would actually also
>>> move them into a separate artifact group.  Currently they use the
>>> group ID org.apache.camel, so we could move them into
>>> org.apache.camel.example or similar.
>>>
>>> I will re-cut the release candidate tonight.
>>>
>>> Thanks,
>>> Gregor
>>>
>>>
>>> On Mon, Apr 24, 2017 at 10:49 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>> Hi Gregor
>>>>
>>>> So we have now fixed this by turning of those connector examples as
>>>> they should not be in the release.
>>>>
>>>> We will later re-organize this and see what to do if any of this is
>>>> needed as releases JAR in maven central.
>>>> You could consider the same for the regular examples, they should
>>>> maybe not be released either to maven central.
>>>> But its a talk for another day.
>>>>
>>>> The master branch should be ready for a re-cut of the release.
>>>>
>>>> Let us know when you are able to work on this again. Thanks a lot for
>>>> helping with the releases.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, Apr 24, 2017 at 10:22 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>> Hi Gregor
>>>>>
>>>>> Okay so the connector examples are not yet intended for release (if
>>>>> they ever would be).
>>>>> So I have skipped them.
>>>>>
>>>>> People can try them from the source code as they do with the other
>>>>> examples. That works fine.
>>>>>
>>>>> For a release process we may also need to add some extra logic so the
>>>>> SNAPSHOT versions in the json files etc are replaced as part of a
>>>>> release build. AFAIR you need to run 2 x build, to make it updated,
>>>>> which you can't usually.
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Apr 23, 2017 at 10:25 PM, Gregor Zurowski
>>>>> <gr...@list.zurowski.org> wrote:
>>>>>> Hi Everyone:
>>>>>>
>>>>>> I have finally managed to resolve all memory-related and
>>>>>> machine-related issues, but I am hitting another road block in the
>>>>>> release process.  The process fails when the new connector examples
>>>>>> are about to get pushed to the artifact repository:
>>>>>>
>>>>>> [INFO] [ERROR] Failed to execute goal
>>>>>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
>>>>>> (default-deploy) on project beverage-component: Failed to deploy
>>>>>> artifacts: Could not transfer artifact
>>>>>> org.foo:beverage-component:jar:2.19.0 from/to apache.releases.https
>>>>>> (https://repository.apache.org/service/local/staging/deploy/maven2):
>>>>>> Failed to transfer file:
>>>>>> https://repository.apache.org/service/local/staging/deploy/maven2/org/foo/beverage-component/2.19.0/beverage-component-2.19.0.jar.
>>>>>> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
>>>>>>
>>>>>> This is likely caused by the group ID "org.foo" that is used in these
>>>>>> modules, which will not be accepted by the Apache artifact repository.
>>>>>>
>>>>>> I could easily change the group ID of these examples to something like
>>>>>> "org.apache.camel.example.connector".  While attempting to change
>>>>>> this, I realized that there are JSON files in the example directories
>>>>>> that directly reference these artifacts, for example in
>>>>>> /salesforce-upsert-contact-connector/src/main/resources/camel-connector.json:
>>>>>>
>>>>>>   "groupId" : "org.foo",
>>>>>>   "artifactId" : "salesforce-upsert-contact-connector",
>>>>>>   "version" : "2.19.0-SNAPSHOT"
>>>>>>
>>>>>> I can update the group ID here as well, but the release process is not
>>>>>> prepared to handle any of these JSON files for updating the version
>>>>>> elements, i.e. 2.19.0-SNAPSHOT should have been rewritten to 2.19.0
>>>>>> within the release preparation step.
>>>>>>
>>>>>> Please let me know how to proceed here.  Once we resolve this, I will
>>>>>> restart the release.
>>>>>>
>>>>>> Thanks,
>>>>>> Gregor
>>>>>>
>>>>>>
>>>>>> On Sat, Apr 22, 2017 at 3:00 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>> Hi Gregor
>>>>>>>
>>>>>>> Sorry for adding that CS error this morning. I guess the extra text in
>>>>>>> that exception message may have caused the line to be too long?
>>>>>>>
>>>>>>> I noticed some Maven WARNs about some examples was a bit wrong with
>>>>>>> bundle vs jar. So I aligned them and just pushed.
>>>>>>> I will step away from the computer so you should have a quiet time to
>>>>>>> work on the release.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sat, Apr 22, 2017 at 2:52 PM, Gregor Zurowski
>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>> Hi Claus,
>>>>>>>>
>>>>>>>> I am still working on the release, just found some CS issues.
>>>>>>>>
>>>>>>>> I am using a different box now, because the OOME problems were
>>>>>>>> definitely caused by some issues with the machine I was using
>>>>>>>> previously.
>>>>>>>>
>>>>>>>> Will keep you posted.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Gregor
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sat, Apr 22, 2017 at 11:02 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>> Hi
>>>>>>>>>
>>>>>>>>> Building the release candidate takes up a lot of memory and Gregor has
>>>>>>>>> hit a OOME with 6gb.
>>>>>>>>>
>>>>>>>>> We are cleaning up a bit in the project to upgrade some of the maven
>>>>>>>>> plugins to use newer versions and reduce some cruft in the assembly.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sat, Apr 22, 2017 at 9:20 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>> Hi
>>>>>>>>>>
>>>>>>>>>> Looking at the CI tests then they all look good (blue/green)
>>>>>>>>>> https://builds.apache.org/view/A-D/view/Camel/
>>>>>>>>>>
>>>>>>>>>> .. except for the spring-boot tests which had two tests for
>>>>>>>>>> camel-core-xml and camel-spring-dm which does not make sense at all so
>>>>>>>>>> I have removed them. This should make this job blue as well.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Sat, Apr 22, 2017 at 9:13 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>> Hi Gregor
>>>>>>>>>>>
>>>>>>>>>>> I can see you committed some fixed last evening.
>>>>>>>>>>>
>>>>>>>>>>> Do you think that you found all the "bugs" in terms of building a
>>>>>>>>>>> release candidate, or do we have more problems?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Apr 21, 2017 at 9:22 PM, Gregor Zurowski
>>>>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>>>>> Hi Claus,
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks for taking care of this.  I will start building the release
>>>>>>>>>>>> candidate now.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Gregor
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Apr 21, 2017 at 9:11 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>>>> Hi
>>>>>>>>>>>>>
>>>>>>>>>>>>> I have just pushed fixes for RAT license check and CS checkstyle. They
>>>>>>>>>>>>> all pass now.
>>>>>>>>>>>>> I also added a few missing JARs in the release kit (the big
>>>>>>>>>>>>> zip/tarball with all the JARs)
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
>>>>>>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>>>>>>> Hi Everyone,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> That is great to hear, I will create the release candidate over the
>>>>>>>>>>>>>> weekend, if all fixes are available on the master branch.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>> Gregor
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart <zo...@regvart.com> wrote:
>>>>>>>>>>>>>>> Hi Cameleers,
>>>>>>>>>>>>>>> Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> thank you :)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> zoran
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>>>>>>> And Zoran has CAMEL-11181 outstanding.
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Zoran Regvart
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Claus Ibsen
>>>>>>>>>>>>> -----------------
>>>>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Claus Ibsen
>>>>>>>>>>> -----------------
>>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Claus Ibsen
>>>>>>>>>> -----------------
>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Claus Ibsen
>>>>>>>>> -----------------
>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Claus Ibsen
>>>>>>> -----------------
>>>>>>> http://davsclaus.com @davsclaus
>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Luca Burgazzoli <lb...@gmail.com>.
Hi Gregor,

I've committed my fixes.



---
Luca Burgazzoli


On Mon, Apr 24, 2017 at 6:10 PM, Luca Burgazzoli <lb...@gmail.com> wrote:
> Hi Gregor,
>
> I'm running a local build to see if there is any blocking issue some
> JIRA I'd like to include [1][2][3], it should not take too much and
> I'll post here as son  as I have merged my work on master.
>
>
> [1] https://issues.apache.org/jira/browse/CAMEL-11190
> [2] https://issues.apache.org/jira/browse/CAMEL-11191
> [3] https://issues.apache.org/jira/browse/CAMEL-11192
>
>
> ---
> Luca Burgazzoli
>
>
> On Mon, Apr 24, 2017 at 11:11 AM, Gregor Zurowski
> <gr...@list.zurowski.org> wrote:
>> Hi Claus,
>>
>> Alright, I guess this is the best we can do for now.  I also agree on
>> removing the regular examples from the release.  I would actually also
>> move them into a separate artifact group.  Currently they use the
>> group ID org.apache.camel, so we could move them into
>> org.apache.camel.example or similar.
>>
>> I will re-cut the release candidate tonight.
>>
>> Thanks,
>> Gregor
>>
>>
>> On Mon, Apr 24, 2017 at 10:49 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>> Hi Gregor
>>>
>>> So we have now fixed this by turning of those connector examples as
>>> they should not be in the release.
>>>
>>> We will later re-organize this and see what to do if any of this is
>>> needed as releases JAR in maven central.
>>> You could consider the same for the regular examples, they should
>>> maybe not be released either to maven central.
>>> But its a talk for another day.
>>>
>>> The master branch should be ready for a re-cut of the release.
>>>
>>> Let us know when you are able to work on this again. Thanks a lot for
>>> helping with the releases.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Apr 24, 2017 at 10:22 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>> Hi Gregor
>>>>
>>>> Okay so the connector examples are not yet intended for release (if
>>>> they ever would be).
>>>> So I have skipped them.
>>>>
>>>> People can try them from the source code as they do with the other
>>>> examples. That works fine.
>>>>
>>>> For a release process we may also need to add some extra logic so the
>>>> SNAPSHOT versions in the json files etc are replaced as part of a
>>>> release build. AFAIR you need to run 2 x build, to make it updated,
>>>> which you can't usually.
>>>>
>>>>
>>>>
>>>> On Sun, Apr 23, 2017 at 10:25 PM, Gregor Zurowski
>>>> <gr...@list.zurowski.org> wrote:
>>>>> Hi Everyone:
>>>>>
>>>>> I have finally managed to resolve all memory-related and
>>>>> machine-related issues, but I am hitting another road block in the
>>>>> release process.  The process fails when the new connector examples
>>>>> are about to get pushed to the artifact repository:
>>>>>
>>>>> [INFO] [ERROR] Failed to execute goal
>>>>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
>>>>> (default-deploy) on project beverage-component: Failed to deploy
>>>>> artifacts: Could not transfer artifact
>>>>> org.foo:beverage-component:jar:2.19.0 from/to apache.releases.https
>>>>> (https://repository.apache.org/service/local/staging/deploy/maven2):
>>>>> Failed to transfer file:
>>>>> https://repository.apache.org/service/local/staging/deploy/maven2/org/foo/beverage-component/2.19.0/beverage-component-2.19.0.jar.
>>>>> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
>>>>>
>>>>> This is likely caused by the group ID "org.foo" that is used in these
>>>>> modules, which will not be accepted by the Apache artifact repository.
>>>>>
>>>>> I could easily change the group ID of these examples to something like
>>>>> "org.apache.camel.example.connector".  While attempting to change
>>>>> this, I realized that there are JSON files in the example directories
>>>>> that directly reference these artifacts, for example in
>>>>> /salesforce-upsert-contact-connector/src/main/resources/camel-connector.json:
>>>>>
>>>>>   "groupId" : "org.foo",
>>>>>   "artifactId" : "salesforce-upsert-contact-connector",
>>>>>   "version" : "2.19.0-SNAPSHOT"
>>>>>
>>>>> I can update the group ID here as well, but the release process is not
>>>>> prepared to handle any of these JSON files for updating the version
>>>>> elements, i.e. 2.19.0-SNAPSHOT should have been rewritten to 2.19.0
>>>>> within the release preparation step.
>>>>>
>>>>> Please let me know how to proceed here.  Once we resolve this, I will
>>>>> restart the release.
>>>>>
>>>>> Thanks,
>>>>> Gregor
>>>>>
>>>>>
>>>>> On Sat, Apr 22, 2017 at 3:00 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>> Hi Gregor
>>>>>>
>>>>>> Sorry for adding that CS error this morning. I guess the extra text in
>>>>>> that exception message may have caused the line to be too long?
>>>>>>
>>>>>> I noticed some Maven WARNs about some examples was a bit wrong with
>>>>>> bundle vs jar. So I aligned them and just pushed.
>>>>>> I will step away from the computer so you should have a quiet time to
>>>>>> work on the release.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sat, Apr 22, 2017 at 2:52 PM, Gregor Zurowski
>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>> Hi Claus,
>>>>>>>
>>>>>>> I am still working on the release, just found some CS issues.
>>>>>>>
>>>>>>> I am using a different box now, because the OOME problems were
>>>>>>> definitely caused by some issues with the machine I was using
>>>>>>> previously.
>>>>>>>
>>>>>>> Will keep you posted.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Gregor
>>>>>>>
>>>>>>>
>>>>>>> On Sat, Apr 22, 2017 at 11:02 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> Building the release candidate takes up a lot of memory and Gregor has
>>>>>>>> hit a OOME with 6gb.
>>>>>>>>
>>>>>>>> We are cleaning up a bit in the project to upgrade some of the maven
>>>>>>>> plugins to use newer versions and reduce some cruft in the assembly.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sat, Apr 22, 2017 at 9:20 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>> Hi
>>>>>>>>>
>>>>>>>>> Looking at the CI tests then they all look good (blue/green)
>>>>>>>>> https://builds.apache.org/view/A-D/view/Camel/
>>>>>>>>>
>>>>>>>>> .. except for the spring-boot tests which had two tests for
>>>>>>>>> camel-core-xml and camel-spring-dm which does not make sense at all so
>>>>>>>>> I have removed them. This should make this job blue as well.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sat, Apr 22, 2017 at 9:13 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>> Hi Gregor
>>>>>>>>>>
>>>>>>>>>> I can see you committed some fixed last evening.
>>>>>>>>>>
>>>>>>>>>> Do you think that you found all the "bugs" in terms of building a
>>>>>>>>>> release candidate, or do we have more problems?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Fri, Apr 21, 2017 at 9:22 PM, Gregor Zurowski
>>>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>>>> Hi Claus,
>>>>>>>>>>>
>>>>>>>>>>> Thanks for taking care of this.  I will start building the release
>>>>>>>>>>> candidate now.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Gregor
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Apr 21, 2017 at 9:11 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>>> Hi
>>>>>>>>>>>>
>>>>>>>>>>>> I have just pushed fixes for RAT license check and CS checkstyle. They
>>>>>>>>>>>> all pass now.
>>>>>>>>>>>> I also added a few missing JARs in the release kit (the big
>>>>>>>>>>>> zip/tarball with all the JARs)
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
>>>>>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>>>>>> Hi Everyone,
>>>>>>>>>>>>>
>>>>>>>>>>>>> That is great to hear, I will create the release candidate over the
>>>>>>>>>>>>> weekend, if all fixes are available on the master branch.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Gregor
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart <zo...@regvart.com> wrote:
>>>>>>>>>>>>>> Hi Cameleers,
>>>>>>>>>>>>>> Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> thank you :)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> zoran
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>>>>>> And Zoran has CAMEL-11181 outstanding.
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Zoran Regvart
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Claus Ibsen
>>>>>>>>>>>> -----------------
>>>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Claus Ibsen
>>>>>>>>>> -----------------
>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Claus Ibsen
>>>>>>>>> -----------------
>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Claus Ibsen
>>>>>>>> -----------------
>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> http://davsclaus.com @davsclaus
>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Luca Burgazzoli <lb...@gmail.com>.
Hi Gregor,

I'm running a local build to see if there is any blocking issue some
JIRA I'd like to include [1][2][3], it should not take too much and
I'll post here as son  as I have merged my work on master.


[1] https://issues.apache.org/jira/browse/CAMEL-11190
[2] https://issues.apache.org/jira/browse/CAMEL-11191
[3] https://issues.apache.org/jira/browse/CAMEL-11192


---
Luca Burgazzoli


On Mon, Apr 24, 2017 at 11:11 AM, Gregor Zurowski
<gr...@list.zurowski.org> wrote:
> Hi Claus,
>
> Alright, I guess this is the best we can do for now.  I also agree on
> removing the regular examples from the release.  I would actually also
> move them into a separate artifact group.  Currently they use the
> group ID org.apache.camel, so we could move them into
> org.apache.camel.example or similar.
>
> I will re-cut the release candidate tonight.
>
> Thanks,
> Gregor
>
>
> On Mon, Apr 24, 2017 at 10:49 AM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi Gregor
>>
>> So we have now fixed this by turning of those connector examples as
>> they should not be in the release.
>>
>> We will later re-organize this and see what to do if any of this is
>> needed as releases JAR in maven central.
>> You could consider the same for the regular examples, they should
>> maybe not be released either to maven central.
>> But its a talk for another day.
>>
>> The master branch should be ready for a re-cut of the release.
>>
>> Let us know when you are able to work on this again. Thanks a lot for
>> helping with the releases.
>>
>>
>>
>>
>>
>>
>>
>>
>> On Mon, Apr 24, 2017 at 10:22 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>> Hi Gregor
>>>
>>> Okay so the connector examples are not yet intended for release (if
>>> they ever would be).
>>> So I have skipped them.
>>>
>>> People can try them from the source code as they do with the other
>>> examples. That works fine.
>>>
>>> For a release process we may also need to add some extra logic so the
>>> SNAPSHOT versions in the json files etc are replaced as part of a
>>> release build. AFAIR you need to run 2 x build, to make it updated,
>>> which you can't usually.
>>>
>>>
>>>
>>> On Sun, Apr 23, 2017 at 10:25 PM, Gregor Zurowski
>>> <gr...@list.zurowski.org> wrote:
>>>> Hi Everyone:
>>>>
>>>> I have finally managed to resolve all memory-related and
>>>> machine-related issues, but I am hitting another road block in the
>>>> release process.  The process fails when the new connector examples
>>>> are about to get pushed to the artifact repository:
>>>>
>>>> [INFO] [ERROR] Failed to execute goal
>>>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
>>>> (default-deploy) on project beverage-component: Failed to deploy
>>>> artifacts: Could not transfer artifact
>>>> org.foo:beverage-component:jar:2.19.0 from/to apache.releases.https
>>>> (https://repository.apache.org/service/local/staging/deploy/maven2):
>>>> Failed to transfer file:
>>>> https://repository.apache.org/service/local/staging/deploy/maven2/org/foo/beverage-component/2.19.0/beverage-component-2.19.0.jar.
>>>> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
>>>>
>>>> This is likely caused by the group ID "org.foo" that is used in these
>>>> modules, which will not be accepted by the Apache artifact repository.
>>>>
>>>> I could easily change the group ID of these examples to something like
>>>> "org.apache.camel.example.connector".  While attempting to change
>>>> this, I realized that there are JSON files in the example directories
>>>> that directly reference these artifacts, for example in
>>>> /salesforce-upsert-contact-connector/src/main/resources/camel-connector.json:
>>>>
>>>>   "groupId" : "org.foo",
>>>>   "artifactId" : "salesforce-upsert-contact-connector",
>>>>   "version" : "2.19.0-SNAPSHOT"
>>>>
>>>> I can update the group ID here as well, but the release process is not
>>>> prepared to handle any of these JSON files for updating the version
>>>> elements, i.e. 2.19.0-SNAPSHOT should have been rewritten to 2.19.0
>>>> within the release preparation step.
>>>>
>>>> Please let me know how to proceed here.  Once we resolve this, I will
>>>> restart the release.
>>>>
>>>> Thanks,
>>>> Gregor
>>>>
>>>>
>>>> On Sat, Apr 22, 2017 at 3:00 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>> Hi Gregor
>>>>>
>>>>> Sorry for adding that CS error this morning. I guess the extra text in
>>>>> that exception message may have caused the line to be too long?
>>>>>
>>>>> I noticed some Maven WARNs about some examples was a bit wrong with
>>>>> bundle vs jar. So I aligned them and just pushed.
>>>>> I will step away from the computer so you should have a quiet time to
>>>>> work on the release.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Sat, Apr 22, 2017 at 2:52 PM, Gregor Zurowski
>>>>> <gr...@list.zurowski.org> wrote:
>>>>>> Hi Claus,
>>>>>>
>>>>>> I am still working on the release, just found some CS issues.
>>>>>>
>>>>>> I am using a different box now, because the OOME problems were
>>>>>> definitely caused by some issues with the machine I was using
>>>>>> previously.
>>>>>>
>>>>>> Will keep you posted.
>>>>>>
>>>>>> Thanks,
>>>>>> Gregor
>>>>>>
>>>>>>
>>>>>> On Sat, Apr 22, 2017 at 11:02 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>> Hi
>>>>>>>
>>>>>>> Building the release candidate takes up a lot of memory and Gregor has
>>>>>>> hit a OOME with 6gb.
>>>>>>>
>>>>>>> We are cleaning up a bit in the project to upgrade some of the maven
>>>>>>> plugins to use newer versions and reduce some cruft in the assembly.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sat, Apr 22, 2017 at 9:20 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> Looking at the CI tests then they all look good (blue/green)
>>>>>>>> https://builds.apache.org/view/A-D/view/Camel/
>>>>>>>>
>>>>>>>> .. except for the spring-boot tests which had two tests for
>>>>>>>> camel-core-xml and camel-spring-dm which does not make sense at all so
>>>>>>>> I have removed them. This should make this job blue as well.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sat, Apr 22, 2017 at 9:13 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>> Hi Gregor
>>>>>>>>>
>>>>>>>>> I can see you committed some fixed last evening.
>>>>>>>>>
>>>>>>>>> Do you think that you found all the "bugs" in terms of building a
>>>>>>>>> release candidate, or do we have more problems?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Fri, Apr 21, 2017 at 9:22 PM, Gregor Zurowski
>>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>>> Hi Claus,
>>>>>>>>>>
>>>>>>>>>> Thanks for taking care of this.  I will start building the release
>>>>>>>>>> candidate now.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Gregor
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Fri, Apr 21, 2017 at 9:11 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>> Hi
>>>>>>>>>>>
>>>>>>>>>>> I have just pushed fixes for RAT license check and CS checkstyle. They
>>>>>>>>>>> all pass now.
>>>>>>>>>>> I also added a few missing JARs in the release kit (the big
>>>>>>>>>>> zip/tarball with all the JARs)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
>>>>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>>>>> Hi Everyone,
>>>>>>>>>>>>
>>>>>>>>>>>> That is great to hear, I will create the release candidate over the
>>>>>>>>>>>> weekend, if all fixes are available on the master branch.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Gregor
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart <zo...@regvart.com> wrote:
>>>>>>>>>>>>> Hi Cameleers,
>>>>>>>>>>>>> Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,
>>>>>>>>>>>>>
>>>>>>>>>>>>> thank you :)
>>>>>>>>>>>>>
>>>>>>>>>>>>> zoran
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>>>>> And Zoran has CAMEL-11181 outstanding.
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Zoran Regvart
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Claus Ibsen
>>>>>>>>>>> -----------------
>>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Claus Ibsen
>>>>>>>>> -----------------
>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Claus Ibsen
>>>>>>>> -----------------
>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Claus Ibsen
>>>>>>> -----------------
>>>>>>> http://davsclaus.com @davsclaus
>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Gregor Zurowski <gr...@list.zurowski.org>.
Hi Claus,

Alright, I guess this is the best we can do for now.  I also agree on
removing the regular examples from the release.  I would actually also
move them into a separate artifact group.  Currently they use the
group ID org.apache.camel, so we could move them into
org.apache.camel.example or similar.

I will re-cut the release candidate tonight.

Thanks,
Gregor


On Mon, Apr 24, 2017 at 10:49 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi Gregor
>
> So we have now fixed this by turning of those connector examples as
> they should not be in the release.
>
> We will later re-organize this and see what to do if any of this is
> needed as releases JAR in maven central.
> You could consider the same for the regular examples, they should
> maybe not be released either to maven central.
> But its a talk for another day.
>
> The master branch should be ready for a re-cut of the release.
>
> Let us know when you are able to work on this again. Thanks a lot for
> helping with the releases.
>
>
>
>
>
>
>
>
> On Mon, Apr 24, 2017 at 10:22 AM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi Gregor
>>
>> Okay so the connector examples are not yet intended for release (if
>> they ever would be).
>> So I have skipped them.
>>
>> People can try them from the source code as they do with the other
>> examples. That works fine.
>>
>> For a release process we may also need to add some extra logic so the
>> SNAPSHOT versions in the json files etc are replaced as part of a
>> release build. AFAIR you need to run 2 x build, to make it updated,
>> which you can't usually.
>>
>>
>>
>> On Sun, Apr 23, 2017 at 10:25 PM, Gregor Zurowski
>> <gr...@list.zurowski.org> wrote:
>>> Hi Everyone:
>>>
>>> I have finally managed to resolve all memory-related and
>>> machine-related issues, but I am hitting another road block in the
>>> release process.  The process fails when the new connector examples
>>> are about to get pushed to the artifact repository:
>>>
>>> [INFO] [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
>>> (default-deploy) on project beverage-component: Failed to deploy
>>> artifacts: Could not transfer artifact
>>> org.foo:beverage-component:jar:2.19.0 from/to apache.releases.https
>>> (https://repository.apache.org/service/local/staging/deploy/maven2):
>>> Failed to transfer file:
>>> https://repository.apache.org/service/local/staging/deploy/maven2/org/foo/beverage-component/2.19.0/beverage-component-2.19.0.jar.
>>> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
>>>
>>> This is likely caused by the group ID "org.foo" that is used in these
>>> modules, which will not be accepted by the Apache artifact repository.
>>>
>>> I could easily change the group ID of these examples to something like
>>> "org.apache.camel.example.connector".  While attempting to change
>>> this, I realized that there are JSON files in the example directories
>>> that directly reference these artifacts, for example in
>>> /salesforce-upsert-contact-connector/src/main/resources/camel-connector.json:
>>>
>>>   "groupId" : "org.foo",
>>>   "artifactId" : "salesforce-upsert-contact-connector",
>>>   "version" : "2.19.0-SNAPSHOT"
>>>
>>> I can update the group ID here as well, but the release process is not
>>> prepared to handle any of these JSON files for updating the version
>>> elements, i.e. 2.19.0-SNAPSHOT should have been rewritten to 2.19.0
>>> within the release preparation step.
>>>
>>> Please let me know how to proceed here.  Once we resolve this, I will
>>> restart the release.
>>>
>>> Thanks,
>>> Gregor
>>>
>>>
>>> On Sat, Apr 22, 2017 at 3:00 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>> Hi Gregor
>>>>
>>>> Sorry for adding that CS error this morning. I guess the extra text in
>>>> that exception message may have caused the line to be too long?
>>>>
>>>> I noticed some Maven WARNs about some examples was a bit wrong with
>>>> bundle vs jar. So I aligned them and just pushed.
>>>> I will step away from the computer so you should have a quiet time to
>>>> work on the release.
>>>>
>>>>
>>>>
>>>>
>>>> On Sat, Apr 22, 2017 at 2:52 PM, Gregor Zurowski
>>>> <gr...@list.zurowski.org> wrote:
>>>>> Hi Claus,
>>>>>
>>>>> I am still working on the release, just found some CS issues.
>>>>>
>>>>> I am using a different box now, because the OOME problems were
>>>>> definitely caused by some issues with the machine I was using
>>>>> previously.
>>>>>
>>>>> Will keep you posted.
>>>>>
>>>>> Thanks,
>>>>> Gregor
>>>>>
>>>>>
>>>>> On Sat, Apr 22, 2017 at 11:02 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>> Hi
>>>>>>
>>>>>> Building the release candidate takes up a lot of memory and Gregor has
>>>>>> hit a OOME with 6gb.
>>>>>>
>>>>>> We are cleaning up a bit in the project to upgrade some of the maven
>>>>>> plugins to use newer versions and reduce some cruft in the assembly.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sat, Apr 22, 2017 at 9:20 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>> Hi
>>>>>>>
>>>>>>> Looking at the CI tests then they all look good (blue/green)
>>>>>>> https://builds.apache.org/view/A-D/view/Camel/
>>>>>>>
>>>>>>> .. except for the spring-boot tests which had two tests for
>>>>>>> camel-core-xml and camel-spring-dm which does not make sense at all so
>>>>>>> I have removed them. This should make this job blue as well.
>>>>>>>
>>>>>>>
>>>>>>> On Sat, Apr 22, 2017 at 9:13 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>> Hi Gregor
>>>>>>>>
>>>>>>>> I can see you committed some fixed last evening.
>>>>>>>>
>>>>>>>> Do you think that you found all the "bugs" in terms of building a
>>>>>>>> release candidate, or do we have more problems?
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, Apr 21, 2017 at 9:22 PM, Gregor Zurowski
>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>> Hi Claus,
>>>>>>>>>
>>>>>>>>> Thanks for taking care of this.  I will start building the release
>>>>>>>>> candidate now.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Gregor
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Fri, Apr 21, 2017 at 9:11 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>> Hi
>>>>>>>>>>
>>>>>>>>>> I have just pushed fixes for RAT license check and CS checkstyle. They
>>>>>>>>>> all pass now.
>>>>>>>>>> I also added a few missing JARs in the release kit (the big
>>>>>>>>>> zip/tarball with all the JARs)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
>>>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>>>> Hi Everyone,
>>>>>>>>>>>
>>>>>>>>>>> That is great to hear, I will create the release candidate over the
>>>>>>>>>>> weekend, if all fixes are available on the master branch.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Gregor
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart <zo...@regvart.com> wrote:
>>>>>>>>>>>> Hi Cameleers,
>>>>>>>>>>>> Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,
>>>>>>>>>>>>
>>>>>>>>>>>> thank you :)
>>>>>>>>>>>>
>>>>>>>>>>>> zoran
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>>>> And Zoran has CAMEL-11181 outstanding.
>>>>>>>>>>>> --
>>>>>>>>>>>> Zoran Regvart
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Claus Ibsen
>>>>>>>>>> -----------------
>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Claus Ibsen
>>>>>>>> -----------------
>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Claus Ibsen
>>>>>>> -----------------
>>>>>>> http://davsclaus.com @davsclaus
>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> http://davsclaus.com @davsclaus
>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Claus Ibsen <cl...@gmail.com>.
Hi Gregor

So we have now fixed this by turning of those connector examples as
they should not be in the release.

We will later re-organize this and see what to do if any of this is
needed as releases JAR in maven central.
You could consider the same for the regular examples, they should
maybe not be released either to maven central.
But its a talk for another day.

The master branch should be ready for a re-cut of the release.

Let us know when you are able to work on this again. Thanks a lot for
helping with the releases.








On Mon, Apr 24, 2017 at 10:22 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi Gregor
>
> Okay so the connector examples are not yet intended for release (if
> they ever would be).
> So I have skipped them.
>
> People can try them from the source code as they do with the other
> examples. That works fine.
>
> For a release process we may also need to add some extra logic so the
> SNAPSHOT versions in the json files etc are replaced as part of a
> release build. AFAIR you need to run 2 x build, to make it updated,
> which you can't usually.
>
>
>
> On Sun, Apr 23, 2017 at 10:25 PM, Gregor Zurowski
> <gr...@list.zurowski.org> wrote:
>> Hi Everyone:
>>
>> I have finally managed to resolve all memory-related and
>> machine-related issues, but I am hitting another road block in the
>> release process.  The process fails when the new connector examples
>> are about to get pushed to the artifact repository:
>>
>> [INFO] [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
>> (default-deploy) on project beverage-component: Failed to deploy
>> artifacts: Could not transfer artifact
>> org.foo:beverage-component:jar:2.19.0 from/to apache.releases.https
>> (https://repository.apache.org/service/local/staging/deploy/maven2):
>> Failed to transfer file:
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/foo/beverage-component/2.19.0/beverage-component-2.19.0.jar.
>> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
>>
>> This is likely caused by the group ID "org.foo" that is used in these
>> modules, which will not be accepted by the Apache artifact repository.
>>
>> I could easily change the group ID of these examples to something like
>> "org.apache.camel.example.connector".  While attempting to change
>> this, I realized that there are JSON files in the example directories
>> that directly reference these artifacts, for example in
>> /salesforce-upsert-contact-connector/src/main/resources/camel-connector.json:
>>
>>   "groupId" : "org.foo",
>>   "artifactId" : "salesforce-upsert-contact-connector",
>>   "version" : "2.19.0-SNAPSHOT"
>>
>> I can update the group ID here as well, but the release process is not
>> prepared to handle any of these JSON files for updating the version
>> elements, i.e. 2.19.0-SNAPSHOT should have been rewritten to 2.19.0
>> within the release preparation step.
>>
>> Please let me know how to proceed here.  Once we resolve this, I will
>> restart the release.
>>
>> Thanks,
>> Gregor
>>
>>
>> On Sat, Apr 22, 2017 at 3:00 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>> Hi Gregor
>>>
>>> Sorry for adding that CS error this morning. I guess the extra text in
>>> that exception message may have caused the line to be too long?
>>>
>>> I noticed some Maven WARNs about some examples was a bit wrong with
>>> bundle vs jar. So I aligned them and just pushed.
>>> I will step away from the computer so you should have a quiet time to
>>> work on the release.
>>>
>>>
>>>
>>>
>>> On Sat, Apr 22, 2017 at 2:52 PM, Gregor Zurowski
>>> <gr...@list.zurowski.org> wrote:
>>>> Hi Claus,
>>>>
>>>> I am still working on the release, just found some CS issues.
>>>>
>>>> I am using a different box now, because the OOME problems were
>>>> definitely caused by some issues with the machine I was using
>>>> previously.
>>>>
>>>> Will keep you posted.
>>>>
>>>> Thanks,
>>>> Gregor
>>>>
>>>>
>>>> On Sat, Apr 22, 2017 at 11:02 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>> Hi
>>>>>
>>>>> Building the release candidate takes up a lot of memory and Gregor has
>>>>> hit a OOME with 6gb.
>>>>>
>>>>> We are cleaning up a bit in the project to upgrade some of the maven
>>>>> plugins to use newer versions and reduce some cruft in the assembly.
>>>>>
>>>>>
>>>>>
>>>>> On Sat, Apr 22, 2017 at 9:20 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>> Hi
>>>>>>
>>>>>> Looking at the CI tests then they all look good (blue/green)
>>>>>> https://builds.apache.org/view/A-D/view/Camel/
>>>>>>
>>>>>> .. except for the spring-boot tests which had two tests for
>>>>>> camel-core-xml and camel-spring-dm which does not make sense at all so
>>>>>> I have removed them. This should make this job blue as well.
>>>>>>
>>>>>>
>>>>>> On Sat, Apr 22, 2017 at 9:13 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>> Hi Gregor
>>>>>>>
>>>>>>> I can see you committed some fixed last evening.
>>>>>>>
>>>>>>> Do you think that you found all the "bugs" in terms of building a
>>>>>>> release candidate, or do we have more problems?
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Apr 21, 2017 at 9:22 PM, Gregor Zurowski
>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>> Hi Claus,
>>>>>>>>
>>>>>>>> Thanks for taking care of this.  I will start building the release
>>>>>>>> candidate now.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Gregor
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, Apr 21, 2017 at 9:11 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>> Hi
>>>>>>>>>
>>>>>>>>> I have just pushed fixes for RAT license check and CS checkstyle. They
>>>>>>>>> all pass now.
>>>>>>>>> I also added a few missing JARs in the release kit (the big
>>>>>>>>> zip/tarball with all the JARs)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
>>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>>> Hi Everyone,
>>>>>>>>>>
>>>>>>>>>> That is great to hear, I will create the release candidate over the
>>>>>>>>>> weekend, if all fixes are available on the master branch.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Gregor
>>>>>>>>>>
>>>>>>>>>> On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart <zo...@regvart.com> wrote:
>>>>>>>>>>> Hi Cameleers,
>>>>>>>>>>> Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,
>>>>>>>>>>>
>>>>>>>>>>> thank you :)
>>>>>>>>>>>
>>>>>>>>>>> zoran
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>>> And Zoran has CAMEL-11181 outstanding.
>>>>>>>>>>> --
>>>>>>>>>>> Zoran Regvart
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Claus Ibsen
>>>>>>>>> -----------------
>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Claus Ibsen
>>>>>>> -----------------
>>>>>>> http://davsclaus.com @davsclaus
>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> http://davsclaus.com @davsclaus
>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Claus Ibsen <cl...@gmail.com>.
Hi Gregor

Okay so the connector examples are not yet intended for release (if
they ever would be).
So I have skipped them.

People can try them from the source code as they do with the other
examples. That works fine.

For a release process we may also need to add some extra logic so the
SNAPSHOT versions in the json files etc are replaced as part of a
release build. AFAIR you need to run 2 x build, to make it updated,
which you can't usually.



On Sun, Apr 23, 2017 at 10:25 PM, Gregor Zurowski
<gr...@list.zurowski.org> wrote:
> Hi Everyone:
>
> I have finally managed to resolve all memory-related and
> machine-related issues, but I am hitting another road block in the
> release process.  The process fails when the new connector examples
> are about to get pushed to the artifact repository:
>
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> (default-deploy) on project beverage-component: Failed to deploy
> artifacts: Could not transfer artifact
> org.foo:beverage-component:jar:2.19.0 from/to apache.releases.https
> (https://repository.apache.org/service/local/staging/deploy/maven2):
> Failed to transfer file:
> https://repository.apache.org/service/local/staging/deploy/maven2/org/foo/beverage-component/2.19.0/beverage-component-2.19.0.jar.
> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
>
> This is likely caused by the group ID "org.foo" that is used in these
> modules, which will not be accepted by the Apache artifact repository.
>
> I could easily change the group ID of these examples to something like
> "org.apache.camel.example.connector".  While attempting to change
> this, I realized that there are JSON files in the example directories
> that directly reference these artifacts, for example in
> /salesforce-upsert-contact-connector/src/main/resources/camel-connector.json:
>
>   "groupId" : "org.foo",
>   "artifactId" : "salesforce-upsert-contact-connector",
>   "version" : "2.19.0-SNAPSHOT"
>
> I can update the group ID here as well, but the release process is not
> prepared to handle any of these JSON files for updating the version
> elements, i.e. 2.19.0-SNAPSHOT should have been rewritten to 2.19.0
> within the release preparation step.
>
> Please let me know how to proceed here.  Once we resolve this, I will
> restart the release.
>
> Thanks,
> Gregor
>
>
> On Sat, Apr 22, 2017 at 3:00 PM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi Gregor
>>
>> Sorry for adding that CS error this morning. I guess the extra text in
>> that exception message may have caused the line to be too long?
>>
>> I noticed some Maven WARNs about some examples was a bit wrong with
>> bundle vs jar. So I aligned them and just pushed.
>> I will step away from the computer so you should have a quiet time to
>> work on the release.
>>
>>
>>
>>
>> On Sat, Apr 22, 2017 at 2:52 PM, Gregor Zurowski
>> <gr...@list.zurowski.org> wrote:
>>> Hi Claus,
>>>
>>> I am still working on the release, just found some CS issues.
>>>
>>> I am using a different box now, because the OOME problems were
>>> definitely caused by some issues with the machine I was using
>>> previously.
>>>
>>> Will keep you posted.
>>>
>>> Thanks,
>>> Gregor
>>>
>>>
>>> On Sat, Apr 22, 2017 at 11:02 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>> Hi
>>>>
>>>> Building the release candidate takes up a lot of memory and Gregor has
>>>> hit a OOME with 6gb.
>>>>
>>>> We are cleaning up a bit in the project to upgrade some of the maven
>>>> plugins to use newer versions and reduce some cruft in the assembly.
>>>>
>>>>
>>>>
>>>> On Sat, Apr 22, 2017 at 9:20 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>> Hi
>>>>>
>>>>> Looking at the CI tests then they all look good (blue/green)
>>>>> https://builds.apache.org/view/A-D/view/Camel/
>>>>>
>>>>> .. except for the spring-boot tests which had two tests for
>>>>> camel-core-xml and camel-spring-dm which does not make sense at all so
>>>>> I have removed them. This should make this job blue as well.
>>>>>
>>>>>
>>>>> On Sat, Apr 22, 2017 at 9:13 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>> Hi Gregor
>>>>>>
>>>>>> I can see you committed some fixed last evening.
>>>>>>
>>>>>> Do you think that you found all the "bugs" in terms of building a
>>>>>> release candidate, or do we have more problems?
>>>>>>
>>>>>>
>>>>>> On Fri, Apr 21, 2017 at 9:22 PM, Gregor Zurowski
>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>> Hi Claus,
>>>>>>>
>>>>>>> Thanks for taking care of this.  I will start building the release
>>>>>>> candidate now.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Gregor
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Apr 21, 2017 at 9:11 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> I have just pushed fixes for RAT license check and CS checkstyle. They
>>>>>>>> all pass now.
>>>>>>>> I also added a few missing JARs in the release kit (the big
>>>>>>>> zip/tarball with all the JARs)
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>> Hi Everyone,
>>>>>>>>>
>>>>>>>>> That is great to hear, I will create the release candidate over the
>>>>>>>>> weekend, if all fixes are available on the master branch.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Gregor
>>>>>>>>>
>>>>>>>>> On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart <zo...@regvart.com> wrote:
>>>>>>>>>> Hi Cameleers,
>>>>>>>>>> Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,
>>>>>>>>>>
>>>>>>>>>> thank you :)
>>>>>>>>>>
>>>>>>>>>> zoran
>>>>>>>>>>
>>>>>>>>>> On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>> And Zoran has CAMEL-11181 outstanding.
>>>>>>>>>> --
>>>>>>>>>> Zoran Regvart
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Claus Ibsen
>>>>>>>> -----------------
>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> http://davsclaus.com @davsclaus
>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

I think you would need to deploy them if you build them locally, so
they can find it in the local m2 repo.

We deploy and ship all the examples
https://github.com/apache/camel/tree/master/examples

... which end up in maven central.
http://search.maven.org/#search%7Cga%7C1%7Ccamel-example





On Mon, Apr 24, 2017 at 9:55 AM, Zoran Regvart <zo...@regvart.com> wrote:
> Hi Gregor & Claus,
> I don't see much use for exaples in the repository, would the
> pragmatic solution be not to publish examples to the repository at
> all? We can skip the deploy plugin[1] it in the examples and
> connector-examples POMs?
>
> zoran
>
> [1] https://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
> --
> Zoran Regvart



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Zoran Regvart <zo...@regvart.com>.
Hi Gregor & Claus,
I don't see much use for exaples in the repository, would the
pragmatic solution be not to publish examples to the repository at
all? We can skip the deploy plugin[1] it in the examples and
connector-examples POMs?

zoran

[1] https://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
-- 
Zoran Regvart

Re: Camel 2.19 Roadmap

Posted by Claus Ibsen <cl...@gmail.com>.
Hi Gregor

I will take a look at this, and report back.

On Sun, Apr 23, 2017 at 10:25 PM, Gregor Zurowski
<gr...@list.zurowski.org> wrote:
> Hi Everyone:
>
> I have finally managed to resolve all memory-related and
> machine-related issues, but I am hitting another road block in the
> release process.  The process fails when the new connector examples
> are about to get pushed to the artifact repository:
>
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> (default-deploy) on project beverage-component: Failed to deploy
> artifacts: Could not transfer artifact
> org.foo:beverage-component:jar:2.19.0 from/to apache.releases.https
> (https://repository.apache.org/service/local/staging/deploy/maven2):
> Failed to transfer file:
> https://repository.apache.org/service/local/staging/deploy/maven2/org/foo/beverage-component/2.19.0/beverage-component-2.19.0.jar.
> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
>
> This is likely caused by the group ID "org.foo" that is used in these
> modules, which will not be accepted by the Apache artifact repository.
>
> I could easily change the group ID of these examples to something like
> "org.apache.camel.example.connector".  While attempting to change
> this, I realized that there are JSON files in the example directories
> that directly reference these artifacts, for example in
> /salesforce-upsert-contact-connector/src/main/resources/camel-connector.json:
>
>   "groupId" : "org.foo",
>   "artifactId" : "salesforce-upsert-contact-connector",
>   "version" : "2.19.0-SNAPSHOT"
>
> I can update the group ID here as well, but the release process is not
> prepared to handle any of these JSON files for updating the version
> elements, i.e. 2.19.0-SNAPSHOT should have been rewritten to 2.19.0
> within the release preparation step.
>
> Please let me know how to proceed here.  Once we resolve this, I will
> restart the release.
>
> Thanks,
> Gregor
>
>
> On Sat, Apr 22, 2017 at 3:00 PM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi Gregor
>>
>> Sorry for adding that CS error this morning. I guess the extra text in
>> that exception message may have caused the line to be too long?
>>
>> I noticed some Maven WARNs about some examples was a bit wrong with
>> bundle vs jar. So I aligned them and just pushed.
>> I will step away from the computer so you should have a quiet time to
>> work on the release.
>>
>>
>>
>>
>> On Sat, Apr 22, 2017 at 2:52 PM, Gregor Zurowski
>> <gr...@list.zurowski.org> wrote:
>>> Hi Claus,
>>>
>>> I am still working on the release, just found some CS issues.
>>>
>>> I am using a different box now, because the OOME problems were
>>> definitely caused by some issues with the machine I was using
>>> previously.
>>>
>>> Will keep you posted.
>>>
>>> Thanks,
>>> Gregor
>>>
>>>
>>> On Sat, Apr 22, 2017 at 11:02 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>> Hi
>>>>
>>>> Building the release candidate takes up a lot of memory and Gregor has
>>>> hit a OOME with 6gb.
>>>>
>>>> We are cleaning up a bit in the project to upgrade some of the maven
>>>> plugins to use newer versions and reduce some cruft in the assembly.
>>>>
>>>>
>>>>
>>>> On Sat, Apr 22, 2017 at 9:20 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>> Hi
>>>>>
>>>>> Looking at the CI tests then they all look good (blue/green)
>>>>> https://builds.apache.org/view/A-D/view/Camel/
>>>>>
>>>>> .. except for the spring-boot tests which had two tests for
>>>>> camel-core-xml and camel-spring-dm which does not make sense at all so
>>>>> I have removed them. This should make this job blue as well.
>>>>>
>>>>>
>>>>> On Sat, Apr 22, 2017 at 9:13 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>> Hi Gregor
>>>>>>
>>>>>> I can see you committed some fixed last evening.
>>>>>>
>>>>>> Do you think that you found all the "bugs" in terms of building a
>>>>>> release candidate, or do we have more problems?
>>>>>>
>>>>>>
>>>>>> On Fri, Apr 21, 2017 at 9:22 PM, Gregor Zurowski
>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>> Hi Claus,
>>>>>>>
>>>>>>> Thanks for taking care of this.  I will start building the release
>>>>>>> candidate now.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Gregor
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Apr 21, 2017 at 9:11 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> I have just pushed fixes for RAT license check and CS checkstyle. They
>>>>>>>> all pass now.
>>>>>>>> I also added a few missing JARs in the release kit (the big
>>>>>>>> zip/tarball with all the JARs)
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>> Hi Everyone,
>>>>>>>>>
>>>>>>>>> That is great to hear, I will create the release candidate over the
>>>>>>>>> weekend, if all fixes are available on the master branch.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Gregor
>>>>>>>>>
>>>>>>>>> On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart <zo...@regvart.com> wrote:
>>>>>>>>>> Hi Cameleers,
>>>>>>>>>> Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,
>>>>>>>>>>
>>>>>>>>>> thank you :)
>>>>>>>>>>
>>>>>>>>>> zoran
>>>>>>>>>>
>>>>>>>>>> On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>> And Zoran has CAMEL-11181 outstanding.
>>>>>>>>>> --
>>>>>>>>>> Zoran Regvart
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Claus Ibsen
>>>>>>>> -----------------
>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> http://davsclaus.com @davsclaus
>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Gregor Zurowski <gr...@list.zurowski.org>.
Hi Everyone:

I have finally managed to resolve all memory-related and
machine-related issues, but I am hitting another road block in the
release process.  The process fails when the new connector examples
are about to get pushed to the artifact repository:

[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
(default-deploy) on project beverage-component: Failed to deploy
artifacts: Could not transfer artifact
org.foo:beverage-component:jar:2.19.0 from/to apache.releases.https
(https://repository.apache.org/service/local/staging/deploy/maven2):
Failed to transfer file:
https://repository.apache.org/service/local/staging/deploy/maven2/org/foo/beverage-component/2.19.0/beverage-component-2.19.0.jar.
Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]

This is likely caused by the group ID "org.foo" that is used in these
modules, which will not be accepted by the Apache artifact repository.

I could easily change the group ID of these examples to something like
"org.apache.camel.example.connector".  While attempting to change
this, I realized that there are JSON files in the example directories
that directly reference these artifacts, for example in
/salesforce-upsert-contact-connector/src/main/resources/camel-connector.json:

  "groupId" : "org.foo",
  "artifactId" : "salesforce-upsert-contact-connector",
  "version" : "2.19.0-SNAPSHOT"

I can update the group ID here as well, but the release process is not
prepared to handle any of these JSON files for updating the version
elements, i.e. 2.19.0-SNAPSHOT should have been rewritten to 2.19.0
within the release preparation step.

Please let me know how to proceed here.  Once we resolve this, I will
restart the release.

Thanks,
Gregor


On Sat, Apr 22, 2017 at 3:00 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi Gregor
>
> Sorry for adding that CS error this morning. I guess the extra text in
> that exception message may have caused the line to be too long?
>
> I noticed some Maven WARNs about some examples was a bit wrong with
> bundle vs jar. So I aligned them and just pushed.
> I will step away from the computer so you should have a quiet time to
> work on the release.
>
>
>
>
> On Sat, Apr 22, 2017 at 2:52 PM, Gregor Zurowski
> <gr...@list.zurowski.org> wrote:
>> Hi Claus,
>>
>> I am still working on the release, just found some CS issues.
>>
>> I am using a different box now, because the OOME problems were
>> definitely caused by some issues with the machine I was using
>> previously.
>>
>> Will keep you posted.
>>
>> Thanks,
>> Gregor
>>
>>
>> On Sat, Apr 22, 2017 at 11:02 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>> Hi
>>>
>>> Building the release candidate takes up a lot of memory and Gregor has
>>> hit a OOME with 6gb.
>>>
>>> We are cleaning up a bit in the project to upgrade some of the maven
>>> plugins to use newer versions and reduce some cruft in the assembly.
>>>
>>>
>>>
>>> On Sat, Apr 22, 2017 at 9:20 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>> Hi
>>>>
>>>> Looking at the CI tests then they all look good (blue/green)
>>>> https://builds.apache.org/view/A-D/view/Camel/
>>>>
>>>> .. except for the spring-boot tests which had two tests for
>>>> camel-core-xml and camel-spring-dm which does not make sense at all so
>>>> I have removed them. This should make this job blue as well.
>>>>
>>>>
>>>> On Sat, Apr 22, 2017 at 9:13 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>> Hi Gregor
>>>>>
>>>>> I can see you committed some fixed last evening.
>>>>>
>>>>> Do you think that you found all the "bugs" in terms of building a
>>>>> release candidate, or do we have more problems?
>>>>>
>>>>>
>>>>> On Fri, Apr 21, 2017 at 9:22 PM, Gregor Zurowski
>>>>> <gr...@list.zurowski.org> wrote:
>>>>>> Hi Claus,
>>>>>>
>>>>>> Thanks for taking care of this.  I will start building the release
>>>>>> candidate now.
>>>>>>
>>>>>> Thanks,
>>>>>> Gregor
>>>>>>
>>>>>>
>>>>>> On Fri, Apr 21, 2017 at 9:11 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>> Hi
>>>>>>>
>>>>>>> I have just pushed fixes for RAT license check and CS checkstyle. They
>>>>>>> all pass now.
>>>>>>> I also added a few missing JARs in the release kit (the big
>>>>>>> zip/tarball with all the JARs)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>> Hi Everyone,
>>>>>>>>
>>>>>>>> That is great to hear, I will create the release candidate over the
>>>>>>>> weekend, if all fixes are available on the master branch.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Gregor
>>>>>>>>
>>>>>>>> On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart <zo...@regvart.com> wrote:
>>>>>>>>> Hi Cameleers,
>>>>>>>>> Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,
>>>>>>>>>
>>>>>>>>> thank you :)
>>>>>>>>>
>>>>>>>>> zoran
>>>>>>>>>
>>>>>>>>> On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>> And Zoran has CAMEL-11181 outstanding.
>>>>>>>>> --
>>>>>>>>> Zoran Regvart
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Claus Ibsen
>>>>>>> -----------------
>>>>>>> http://davsclaus.com @davsclaus
>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Claus Ibsen <cl...@gmail.com>.
Hi Gregor

Sorry for adding that CS error this morning. I guess the extra text in
that exception message may have caused the line to be too long?

I noticed some Maven WARNs about some examples was a bit wrong with
bundle vs jar. So I aligned them and just pushed.
I will step away from the computer so you should have a quiet time to
work on the release.




On Sat, Apr 22, 2017 at 2:52 PM, Gregor Zurowski
<gr...@list.zurowski.org> wrote:
> Hi Claus,
>
> I am still working on the release, just found some CS issues.
>
> I am using a different box now, because the OOME problems were
> definitely caused by some issues with the machine I was using
> previously.
>
> Will keep you posted.
>
> Thanks,
> Gregor
>
>
> On Sat, Apr 22, 2017 at 11:02 AM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi
>>
>> Building the release candidate takes up a lot of memory and Gregor has
>> hit a OOME with 6gb.
>>
>> We are cleaning up a bit in the project to upgrade some of the maven
>> plugins to use newer versions and reduce some cruft in the assembly.
>>
>>
>>
>> On Sat, Apr 22, 2017 at 9:20 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>> Hi
>>>
>>> Looking at the CI tests then they all look good (blue/green)
>>> https://builds.apache.org/view/A-D/view/Camel/
>>>
>>> .. except for the spring-boot tests which had two tests for
>>> camel-core-xml and camel-spring-dm which does not make sense at all so
>>> I have removed them. This should make this job blue as well.
>>>
>>>
>>> On Sat, Apr 22, 2017 at 9:13 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>> Hi Gregor
>>>>
>>>> I can see you committed some fixed last evening.
>>>>
>>>> Do you think that you found all the "bugs" in terms of building a
>>>> release candidate, or do we have more problems?
>>>>
>>>>
>>>> On Fri, Apr 21, 2017 at 9:22 PM, Gregor Zurowski
>>>> <gr...@list.zurowski.org> wrote:
>>>>> Hi Claus,
>>>>>
>>>>> Thanks for taking care of this.  I will start building the release
>>>>> candidate now.
>>>>>
>>>>> Thanks,
>>>>> Gregor
>>>>>
>>>>>
>>>>> On Fri, Apr 21, 2017 at 9:11 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>> Hi
>>>>>>
>>>>>> I have just pushed fixes for RAT license check and CS checkstyle. They
>>>>>> all pass now.
>>>>>> I also added a few missing JARs in the release kit (the big
>>>>>> zip/tarball with all the JARs)
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>> Hi Everyone,
>>>>>>>
>>>>>>> That is great to hear, I will create the release candidate over the
>>>>>>> weekend, if all fixes are available on the master branch.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Gregor
>>>>>>>
>>>>>>> On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart <zo...@regvart.com> wrote:
>>>>>>>> Hi Cameleers,
>>>>>>>> Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,
>>>>>>>>
>>>>>>>> thank you :)
>>>>>>>>
>>>>>>>> zoran
>>>>>>>>
>>>>>>>> On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>> And Zoran has CAMEL-11181 outstanding.
>>>>>>>> --
>>>>>>>> Zoran Regvart
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> http://davsclaus.com @davsclaus
>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Gregor Zurowski <gr...@list.zurowski.org>.
Hi Claus,

I am still working on the release, just found some CS issues.

I am using a different box now, because the OOME problems were
definitely caused by some issues with the machine I was using
previously.

Will keep you posted.

Thanks,
Gregor


On Sat, Apr 22, 2017 at 11:02 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> Building the release candidate takes up a lot of memory and Gregor has
> hit a OOME with 6gb.
>
> We are cleaning up a bit in the project to upgrade some of the maven
> plugins to use newer versions and reduce some cruft in the assembly.
>
>
>
> On Sat, Apr 22, 2017 at 9:20 AM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi
>>
>> Looking at the CI tests then they all look good (blue/green)
>> https://builds.apache.org/view/A-D/view/Camel/
>>
>> .. except for the spring-boot tests which had two tests for
>> camel-core-xml and camel-spring-dm which does not make sense at all so
>> I have removed them. This should make this job blue as well.
>>
>>
>> On Sat, Apr 22, 2017 at 9:13 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>> Hi Gregor
>>>
>>> I can see you committed some fixed last evening.
>>>
>>> Do you think that you found all the "bugs" in terms of building a
>>> release candidate, or do we have more problems?
>>>
>>>
>>> On Fri, Apr 21, 2017 at 9:22 PM, Gregor Zurowski
>>> <gr...@list.zurowski.org> wrote:
>>>> Hi Claus,
>>>>
>>>> Thanks for taking care of this.  I will start building the release
>>>> candidate now.
>>>>
>>>> Thanks,
>>>> Gregor
>>>>
>>>>
>>>> On Fri, Apr 21, 2017 at 9:11 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>> Hi
>>>>>
>>>>> I have just pushed fixes for RAT license check and CS checkstyle. They
>>>>> all pass now.
>>>>> I also added a few missing JARs in the release kit (the big
>>>>> zip/tarball with all the JARs)
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
>>>>> <gr...@list.zurowski.org> wrote:
>>>>>> Hi Everyone,
>>>>>>
>>>>>> That is great to hear, I will create the release candidate over the
>>>>>> weekend, if all fixes are available on the master branch.
>>>>>>
>>>>>> Thanks,
>>>>>> Gregor
>>>>>>
>>>>>> On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart <zo...@regvart.com> wrote:
>>>>>>> Hi Cameleers,
>>>>>>> Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,
>>>>>>>
>>>>>>> thank you :)
>>>>>>>
>>>>>>> zoran
>>>>>>>
>>>>>>> On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>> And Zoran has CAMEL-11181 outstanding.
>>>>>>> --
>>>>>>> Zoran Regvart
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

Building the release candidate takes up a lot of memory and Gregor has
hit a OOME with 6gb.

We are cleaning up a bit in the project to upgrade some of the maven
plugins to use newer versions and reduce some cruft in the assembly.



On Sat, Apr 22, 2017 at 9:20 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> Looking at the CI tests then they all look good (blue/green)
> https://builds.apache.org/view/A-D/view/Camel/
>
> .. except for the spring-boot tests which had two tests for
> camel-core-xml and camel-spring-dm which does not make sense at all so
> I have removed them. This should make this job blue as well.
>
>
> On Sat, Apr 22, 2017 at 9:13 AM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi Gregor
>>
>> I can see you committed some fixed last evening.
>>
>> Do you think that you found all the "bugs" in terms of building a
>> release candidate, or do we have more problems?
>>
>>
>> On Fri, Apr 21, 2017 at 9:22 PM, Gregor Zurowski
>> <gr...@list.zurowski.org> wrote:
>>> Hi Claus,
>>>
>>> Thanks for taking care of this.  I will start building the release
>>> candidate now.
>>>
>>> Thanks,
>>> Gregor
>>>
>>>
>>> On Fri, Apr 21, 2017 at 9:11 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>> Hi
>>>>
>>>> I have just pushed fixes for RAT license check and CS checkstyle. They
>>>> all pass now.
>>>> I also added a few missing JARs in the release kit (the big
>>>> zip/tarball with all the JARs)
>>>>
>>>>
>>>>
>>>> On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
>>>> <gr...@list.zurowski.org> wrote:
>>>>> Hi Everyone,
>>>>>
>>>>> That is great to hear, I will create the release candidate over the
>>>>> weekend, if all fixes are available on the master branch.
>>>>>
>>>>> Thanks,
>>>>> Gregor
>>>>>
>>>>> On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart <zo...@regvart.com> wrote:
>>>>>> Hi Cameleers,
>>>>>> Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,
>>>>>>
>>>>>> thank you :)
>>>>>>
>>>>>> zoran
>>>>>>
>>>>>> On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>> And Zoran has CAMEL-11181 outstanding.
>>>>>> --
>>>>>> Zoran Regvart
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

Looking at the CI tests then they all look good (blue/green)
https://builds.apache.org/view/A-D/view/Camel/

.. except for the spring-boot tests which had two tests for
camel-core-xml and camel-spring-dm which does not make sense at all so
I have removed them. This should make this job blue as well.


On Sat, Apr 22, 2017 at 9:13 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi Gregor
>
> I can see you committed some fixed last evening.
>
> Do you think that you found all the "bugs" in terms of building a
> release candidate, or do we have more problems?
>
>
> On Fri, Apr 21, 2017 at 9:22 PM, Gregor Zurowski
> <gr...@list.zurowski.org> wrote:
>> Hi Claus,
>>
>> Thanks for taking care of this.  I will start building the release
>> candidate now.
>>
>> Thanks,
>> Gregor
>>
>>
>> On Fri, Apr 21, 2017 at 9:11 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>> Hi
>>>
>>> I have just pushed fixes for RAT license check and CS checkstyle. They
>>> all pass now.
>>> I also added a few missing JARs in the release kit (the big
>>> zip/tarball with all the JARs)
>>>
>>>
>>>
>>> On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
>>> <gr...@list.zurowski.org> wrote:
>>>> Hi Everyone,
>>>>
>>>> That is great to hear, I will create the release candidate over the
>>>> weekend, if all fixes are available on the master branch.
>>>>
>>>> Thanks,
>>>> Gregor
>>>>
>>>> On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart <zo...@regvart.com> wrote:
>>>>> Hi Cameleers,
>>>>> Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,
>>>>>
>>>>> thank you :)
>>>>>
>>>>> zoran
>>>>>
>>>>> On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>> And Zoran has CAMEL-11181 outstanding.
>>>>> --
>>>>> Zoran Regvart
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Claus Ibsen <cl...@gmail.com>.
Hi Gregor

I can see you committed some fixed last evening.

Do you think that you found all the "bugs" in terms of building a
release candidate, or do we have more problems?


On Fri, Apr 21, 2017 at 9:22 PM, Gregor Zurowski
<gr...@list.zurowski.org> wrote:
> Hi Claus,
>
> Thanks for taking care of this.  I will start building the release
> candidate now.
>
> Thanks,
> Gregor
>
>
> On Fri, Apr 21, 2017 at 9:11 PM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi
>>
>> I have just pushed fixes for RAT license check and CS checkstyle. They
>> all pass now.
>> I also added a few missing JARs in the release kit (the big
>> zip/tarball with all the JARs)
>>
>>
>>
>> On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
>> <gr...@list.zurowski.org> wrote:
>>> Hi Everyone,
>>>
>>> That is great to hear, I will create the release candidate over the
>>> weekend, if all fixes are available on the master branch.
>>>
>>> Thanks,
>>> Gregor
>>>
>>> On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart <zo...@regvart.com> wrote:
>>>> Hi Cameleers,
>>>> Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,
>>>>
>>>> thank you :)
>>>>
>>>> zoran
>>>>
>>>> On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>> And Zoran has CAMEL-11181 outstanding.
>>>> --
>>>> Zoran Regvart
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Gregor Zurowski <gr...@list.zurowski.org>.
Hi Claus,

Thanks for taking care of this.  I will start building the release
candidate now.

Thanks,
Gregor


On Fri, Apr 21, 2017 at 9:11 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> I have just pushed fixes for RAT license check and CS checkstyle. They
> all pass now.
> I also added a few missing JARs in the release kit (the big
> zip/tarball with all the JARs)
>
>
>
> On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
> <gr...@list.zurowski.org> wrote:
>> Hi Everyone,
>>
>> That is great to hear, I will create the release candidate over the
>> weekend, if all fixes are available on the master branch.
>>
>> Thanks,
>> Gregor
>>
>> On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart <zo...@regvart.com> wrote:
>>> Hi Cameleers,
>>> Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,
>>>
>>> thank you :)
>>>
>>> zoran
>>>
>>> On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>> And Zoran has CAMEL-11181 outstanding.
>>> --
>>> Zoran Regvart
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

I have just pushed fixes for RAT license check and CS checkstyle. They
all pass now.
I also added a few missing JARs in the release kit (the big
zip/tarball with all the JARs)



On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
<gr...@list.zurowski.org> wrote:
> Hi Everyone,
>
> That is great to hear, I will create the release candidate over the
> weekend, if all fixes are available on the master branch.
>
> Thanks,
> Gregor
>
> On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart <zo...@regvart.com> wrote:
>> Hi Cameleers,
>> Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,
>>
>> thank you :)
>>
>> zoran
>>
>> On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>> And Zoran has CAMEL-11181 outstanding.
>> --
>> Zoran Regvart



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by John Poth <po...@gmail.com>.
I just pushed my Java 9 work and am ready for a release :)

Thanks,
John.

On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski <gr...@list.zurowski.org>
wrote:

> Hi Everyone,
>
> That is great to hear, I will create the release candidate over the
> weekend, if all fixes are available on the master branch.
>
> Thanks,
> Gregor
>
> On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart <zo...@regvart.com> wrote:
> > Hi Cameleers,
> > Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,
> >
> > thank you :)
> >
> > zoran
> >
> > On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen <cl...@gmail.com>
> wrote:
> >> And Zoran has CAMEL-11181 outstanding.
> > --
> > Zoran Regvart
>

Re: Camel 2.19 Roadmap

Posted by Gregor Zurowski <gr...@list.zurowski.org>.
Hi Everyone,

That is great to hear, I will create the release candidate over the
weekend, if all fixes are available on the master branch.

Thanks,
Gregor

On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart <zo...@regvart.com> wrote:
> Hi Cameleers,
> Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,
>
> thank you :)
>
> zoran
>
> On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>> And Zoran has CAMEL-11181 outstanding.
> --
> Zoran Regvart

Re: Camel 2.19 Roadmap

Posted by Zoran Regvart <zo...@regvart.com>.
Hi Cameleers,
Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to master,

thank you :)

zoran

On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
> And Zoran has CAMEL-11181 outstanding.
-- 
Zoran Regvart

Re: Camel 2.19 Roadmap

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

Okay Spring Boot 1.5.3 has been released and we have upgraded to this version.

We are waiting for those java 9 fixes that John will submit later today.
And Zoran has CAMEL-11181 outstanding.

On Fri, Apr 21, 2017 at 10:24 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> So there is some fixed in the works for making the source build on
> Java 9. John will submit a PR later today. We are also waiting for the
> Spring Boot 1.5.3 release. They released 1.4.6 yesterday and are
> working on the 1.5.x release.
>
> The CI servers should still look good but sometimes they cannot
> complete due low on memory or other maven/jenkins troubles. But when
> they get a full build they tend to pass or have very low errors. But
> we should keep an eye on them as well.
>
>
> On Thu, Apr 20, 2017 at 5:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi
>>
>> Okay we are looking in good shape.
>>
>> We are waiting for the new 1.5.3 release of spring boot. They have
>> just released 1.4.6 today.
>>
>> The CI server are blue/green for the last number of builds.
>> But lets keep an eye on them. Ideally we should have java 9 be able to
>> build the source code.
>>
>>
>>
>>
>>
>> On Wed, Apr 19, 2017 at 2:21 PM, Luca Burgazzoli <lb...@gmail.com> wrote:
>>> Hi,
>>>
>>> I have one little refactoring (rename LoadBalancer in camel cloud
>>> package to avoid confusion with LoadBalancer processor) and a little
>>> doc update that I'm trying to make by end of day.
>>>
>>>
>>>
>>> ---
>>> Luca Burgazzoli
>>>
>>>
>>> On Wed, Apr 19, 2017 at 1:39 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>> Hi
>>>>
>>>> So the @Generated and Java 9 ought to be fixed now.
>>>>
>>>> There is a new version of Spring Boot 1.5.3 on the way. It may be
>>>> beneficial to wait for that to be released so we are running on
>>>> latest.
>>>>
>>>> On Wed, Apr 19, 2017 at 9:54 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>> Hi
>>>>>
>>>>> Okay so there is some last minute issues with the @Generated
>>>>> annotations we need to look into
>>>>> https://issues.apache.org/jira/browse/CAMEL-11165
>>>>>
>>>>> And an unforseen effect on java 9 builds
>>>>> https://issues.apache.org/jira/browse/CAMEL-11166
>>>>>
>>>>> The full test is passing now. And the Spring Boot and Karaf tests has
>>>>> also passed but failed recently due some maven download error or some
>>>>> other weird error. So lets kick new builds when we get the 2 tickets
>>>>> resolved above.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Apr 18, 2017 at 9:45 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>> Hi
>>>>>>
>>>>>> Things start to look good. There is a itest that fails with spring
>>>>>> boot which we need to look at and get fixed
>>>>>> https://issues.apache.org/jira/browse/CAMEL-11154
>>>>>>
>>>>>> The other tests was all passing recently and they ought to become blue
>>>>>> again. But lets keep an eye on them:
>>>>>> https://builds.apache.org/view/A-D/view/Camel/
>>>>>>
>>>>>>
>>>>>> On Thu, Apr 13, 2017 at 1:50 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>> Hi
>>>>>>>
>>>>>>> Thanks Antonin that sounds great.
>>>>>>>
>>>>>>> The JIRA tickets are down to 3
>>>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved
>>>>>>>
>>>>>>> We have recently fixed up the missing component docs and fixed broken
>>>>>>> links from browsing on github.
>>>>>>>
>>>>>>> We should keep an eye on the CI servers and output from the
>>>>>>> camel-catalog report, to see if it reports more missing stuff.
>>>>>>> It currently has a false positive on some missing docs for some of the
>>>>>>> test components. I will try to fix this later today.
>>>>>>>
>>>>>>> However thats not all. At all time feel free to have fun and work on
>>>>>>> anything you like on Camel. There is still time for small improvements
>>>>>>> etc. But bigger stuff we should really defer to the next release.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Apr 12, 2017 at 3:35 PM, Antonin Stefanutti
>>>>>>> <an...@stefanutti.fr> wrote:
>>>>>>>>
>>>>>>>>> On 12 Apr 2017, at 15:22, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Hi
>>>>>>>>>
>>>>>>>>> Just a heads up that we plan to cut the RC for Camel 2.19 next week.
>>>>>>>>>
>>>>>>>>> So we are closing down on the last tickets, bugs, features etc to get
>>>>>>>>> the code base in shape.
>>>>>>>>>
>>>>>>>>> The JIRA has 9 tickets
>>>>>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved
>>>>>>>>>
>>>>>>>>> But you are of course welcome to work on other tickets etc but just
>>>>>>>>> mind any big functionality is likely better to wait for next release.
>>>>>>>>>
>>>>>>>>> There is however the expected transaction stuff for CDI as a PR in the
>>>>>>>>> works, and also a new iot component
>>>>>>>>> https://github.com/apache/camel/pulls
>>>>>>>>
>>>>>>>> The CDI transaction support PR should be merged by end of week.
>>>>>>>>
>>>>>>>> https://github.com/apache/camel/pull/1390
>>>>>>>>
>>>>>>>>> We should keep an eye on the CI servers to see how they are and fix
>>>>>>>>> any test failures etc. Recently we got them to build and test the OSGi
>>>>>>>>> and spring-boot specific tests so we should be able to better keep an
>>>>>>>>> eye on this now and in the future.
>>>>>>>>> https://builds.apache.org/view/A-D/view/Camel/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Fri, Apr 7, 2017 at 8:45 AM, Gregor Zurowski
>>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>>> Hi Claus,
>>>>>>>>>>
>>>>>>>>>> Week 16 works for me.  I will send out another email shortly before
>>>>>>>>>> starting to build the RC.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Gregor
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Apr 5, 2017 at 3:08 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>> Hi Gregor
>>>>>>>>>>>
>>>>>>>>>>> Yeah its April so we should get the 2.19.0 release out the door.
>>>>>>>>>>>
>>>>>>>>>>> We have just setup a 2.20.0 version in JIRA and folks should start
>>>>>>>>>>> moving their tickets to that version if its something that they cannot
>>>>>>>>>>> finish in time. Also we should refrain from doing bigger work at this
>>>>>>>>>>> time as we should close down on last tickets, bug fixes, and get the
>>>>>>>>>>> CI tests in good order, etc.
>>>>>>>>>>>
>>>>>>>>>>> I will look at the JIRAs later this week and cleanup a bit so we have
>>>>>>>>>>> a better overview of what work is yet to be done.
>>>>>>>>>>>
>>>>>>>>>>> As April has the easter holidays. I wonder what you time schedule looks like?
>>>>>>>>>>>
>>>>>>>>>>> Maybe if you have time to help with the release after the holidays?
>>>>>>>>>>>
>>>>>>>>>>> Week 16 and 17 are the last 2 weeks in April after the holidays.
>>>>>>>>>>> If we could maybe cut the RC in week 16 then that would be good.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Apr 3, 2017 at 2:14 PM, Gregor Zurowski
>>>>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> Are we getting closer to build a 2.19.0 release?  I would volunteer
>>>>>>>>>>>> for creating the release, just wanted to check when would be a good
>>>>>>>>>>>> time to do so.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Gregor
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Mar 15, 2017 at 9:29 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>>>> Hi
>>>>>>>>>>>>>
>>>>>>>>>>>>> Just wanted to bring up that we are closing in on a good time for
>>>>>>>>>>>>> doing a new release.
>>>>>>>>>>>>>
>>>>>>>>>>>>> For example in mid April it would be around 6 months since the last
>>>>>>>>>>>>> 2.18.0 release.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Therefore we should start closing down and fixing bugs, and make sure
>>>>>>>>>>>>> the CI servers and tests are in good shape.
>>>>>>>>>>>>> This morning we have fixed a number of recent test failures and are
>>>>>>>>>>>>> down to only 1 test failure now.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Jan 16, 2017 at 10:28 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>>>>> Hi
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> There is a bunch of stuff which we can/should have on the roadmap to
>>>>>>>>>>>>>> complete for the Camel 2.19 release.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Here is on top of my head
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 1)
>>>>>>>>>>>>>> Finish migrating the wiki documentation to adoc files. I think its
>>>>>>>>>>>>>> most of the EIP patterns that are missing. There is a basic list of
>>>>>>>>>>>>>> EIPs here: https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2)
>>>>>>>>>>>>>> Generate documentation and website. Maybe documentation first and then
>>>>>>>>>>>>>> we come up with a modern website later - when we have a new logo as
>>>>>>>>>>>>>> well.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 3)
>>>>>>>>>>>>>> Mark more stuff to @deprecate so we dont drag them into Camel 3.0.
>>>>>>>>>>>>>> This is both components / and other artifacts.
>>>>>>>>>>>>>> And as well the camel-core APIs where there is maybe more we can deprecate.
>>>>>>>>>>>>>> For example the old stuff that was created prior to the component docs
>>>>>>>>>>>>>> we do now with the apt plugin at build time instead of this old code
>>>>>>>>>>>>>> with runtime that dont really pan out anyway.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 4)
>>>>>>>>>>>>>> Move spring-boot starters into the platforms folder. There is a ticket
>>>>>>>>>>>>>> about this.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 5)
>>>>>>>>>>>>>> More improvements to spring boot auto configuration. We have a bunch
>>>>>>>>>>>>>> of tickets on that.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 6)
>>>>>>>>>>>>>> Look at the health check API and see if there is something we can get
>>>>>>>>>>>>>> started on.
>>>>>>>>>>>>>> Possible some API to integrate with spring boot actuators (when using
>>>>>>>>>>>>>> SB) and allow each component to provide their own checks so they can
>>>>>>>>>>>>>> be implemented ad-hoc. There is a ticket about this.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 7)
>>>>>>>>>>>>>> Possible some more teaks to camel-catalog based on feedback from IDEA
>>>>>>>>>>>>>> plugin and the maven validate goal.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 8)
>>>>>>>>>>>>>> That CDI JEE transaction PR on github.
>>>>>>>>>>>>>> Ideally we would have had a transaction API in camel-core and then one
>>>>>>>>>>>>>> impl for camel-spring, and then another for camel-cdi-jee. But that
>>>>>>>>>>>>>> may require too much work.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 9)
>>>>>>>>>>>>>> Work on the Java 8 DSL such as get more community feedback, and then
>>>>>>>>>>>>>> resolve the TODOs with the documentation updates and look into other
>>>>>>>>>>>>>> areas where the API can benefit from Java 8 lambdas and whatnot. I
>>>>>>>>>>>>>> dont think we have a ticket about this.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 10)
>>>>>>>>>>>>>> Karaf users may want to improve/finish up the camel-test-karaf module
>>>>>>>>>>>>>> so its more usable and end users can use it to test integration tests
>>>>>>>>>>>>>> with Camel and Karaf.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 11)
>>>>>>>>>>>>>> Introduce Camel Connectors (more about this later)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Anything else?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Claus Ibsen
>>>>>>>>>>>>>> -----------------
>>>>>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Claus Ibsen
>>>>>>>>>>>>> -----------------
>>>>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Claus Ibsen
>>>>>>>>>>> -----------------
>>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Claus Ibsen
>>>>>>>>> -----------------
>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Claus Ibsen
>>>>>>> -----------------
>>>>>>> http://davsclaus.com @davsclaus
>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> http://davsclaus.com @davsclaus
>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Zoran Regvart <zo...@regvart.com>.
Hi Dmitry,
we already have gmavenplus in Salesforce component, I've logged
CAMEL-11181[1] and created a pull request[2], can you help by
reviewing the pull request?

thank you :)

zoran

[1] https://issues.apache.org/jira/browse/CAMEL-11181
[2] https://github.com/apache/camel/pull/1651

On Fri, Apr 21, 2017 at 11:55 AM, Dmitry Volodin <dm...@gmail.com> wrote:
> Hi Zoran!
>
> Thanks a lot for your tips.
> As two latest gmaven plugin usage was introduced by me in camel-protobuf
> and camel-grpc components, I'm able to schedule gmaven -> gmavenplus
> transition in future components improvement.
>
> --
> Best regards,
> Dmitry
>
> 2017-04-21 12:20 GMT+03:00 Zoran Regvart <zo...@regvart.com>:
>
>> Hi Cameleers,
>> we are using gmaven plugin in couple of modules, it seems that going
>> forward it would be better to switch to gmavenplus plugin, well, at
>> least with Java 9 and Jigsaw[1].
>>
>> I would like to make that switch, do you think this is something worth
>> doing, and worth doing in 2.19?
>>
>> zoran
>>
>> [1] https://cwiki.apache.org/confluence/display/MAVEN/Java+
>> 9+-+Jigsaw#Java9-Jigsaw-Thirdpartycomponents
>> --
>> Zoran Regvart
>>



-- 
Zoran Regvart

Re: Camel 2.19 Roadmap

Posted by Dmitry Volodin <dm...@gmail.com>.
Hi Zoran!

Thanks a lot for your tips.
As two latest gmaven plugin usage was introduced by me in camel-protobuf
and camel-grpc components, I'm able to schedule gmaven -> gmavenplus
transition in future components improvement.

--
Best regards,
Dmitry

2017-04-21 12:20 GMT+03:00 Zoran Regvart <zo...@regvart.com>:

> Hi Cameleers,
> we are using gmaven plugin in couple of modules, it seems that going
> forward it would be better to switch to gmavenplus plugin, well, at
> least with Java 9 and Jigsaw[1].
>
> I would like to make that switch, do you think this is something worth
> doing, and worth doing in 2.19?
>
> zoran
>
> [1] https://cwiki.apache.org/confluence/display/MAVEN/Java+
> 9+-+Jigsaw#Java9-Jigsaw-Thirdpartycomponents
> --
> Zoran Regvart
>

Re: Camel 2.19 Roadmap

Posted by Zoran Regvart <zo...@regvart.com>.
Hi Cameleers,
we are using gmaven plugin in couple of modules, it seems that going
forward it would be better to switch to gmavenplus plugin, well, at
least with Java 9 and Jigsaw[1].

I would like to make that switch, do you think this is something worth
doing, and worth doing in 2.19?

zoran

[1] https://cwiki.apache.org/confluence/display/MAVEN/Java+9+-+Jigsaw#Java9-Jigsaw-Thirdpartycomponents
-- 
Zoran Regvart

Re: Camel 2.19 Roadmap

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

So there is some fixed in the works for making the source build on
Java 9. John will submit a PR later today. We are also waiting for the
Spring Boot 1.5.3 release. They released 1.4.6 yesterday and are
working on the 1.5.x release.

The CI servers should still look good but sometimes they cannot
complete due low on memory or other maven/jenkins troubles. But when
they get a full build they tend to pass or have very low errors. But
we should keep an eye on them as well.


On Thu, Apr 20, 2017 at 5:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> Okay we are looking in good shape.
>
> We are waiting for the new 1.5.3 release of spring boot. They have
> just released 1.4.6 today.
>
> The CI server are blue/green for the last number of builds.
> But lets keep an eye on them. Ideally we should have java 9 be able to
> build the source code.
>
>
>
>
>
> On Wed, Apr 19, 2017 at 2:21 PM, Luca Burgazzoli <lb...@gmail.com> wrote:
>> Hi,
>>
>> I have one little refactoring (rename LoadBalancer in camel cloud
>> package to avoid confusion with LoadBalancer processor) and a little
>> doc update that I'm trying to make by end of day.
>>
>>
>>
>> ---
>> Luca Burgazzoli
>>
>>
>> On Wed, Apr 19, 2017 at 1:39 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>> Hi
>>>
>>> So the @Generated and Java 9 ought to be fixed now.
>>>
>>> There is a new version of Spring Boot 1.5.3 on the way. It may be
>>> beneficial to wait for that to be released so we are running on
>>> latest.
>>>
>>> On Wed, Apr 19, 2017 at 9:54 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>> Hi
>>>>
>>>> Okay so there is some last minute issues with the @Generated
>>>> annotations we need to look into
>>>> https://issues.apache.org/jira/browse/CAMEL-11165
>>>>
>>>> And an unforseen effect on java 9 builds
>>>> https://issues.apache.org/jira/browse/CAMEL-11166
>>>>
>>>> The full test is passing now. And the Spring Boot and Karaf tests has
>>>> also passed but failed recently due some maven download error or some
>>>> other weird error. So lets kick new builds when we get the 2 tickets
>>>> resolved above.
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, Apr 18, 2017 at 9:45 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>> Hi
>>>>>
>>>>> Things start to look good. There is a itest that fails with spring
>>>>> boot which we need to look at and get fixed
>>>>> https://issues.apache.org/jira/browse/CAMEL-11154
>>>>>
>>>>> The other tests was all passing recently and they ought to become blue
>>>>> again. But lets keep an eye on them:
>>>>> https://builds.apache.org/view/A-D/view/Camel/
>>>>>
>>>>>
>>>>> On Thu, Apr 13, 2017 at 1:50 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>> Hi
>>>>>>
>>>>>> Thanks Antonin that sounds great.
>>>>>>
>>>>>> The JIRA tickets are down to 3
>>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved
>>>>>>
>>>>>> We have recently fixed up the missing component docs and fixed broken
>>>>>> links from browsing on github.
>>>>>>
>>>>>> We should keep an eye on the CI servers and output from the
>>>>>> camel-catalog report, to see if it reports more missing stuff.
>>>>>> It currently has a false positive on some missing docs for some of the
>>>>>> test components. I will try to fix this later today.
>>>>>>
>>>>>> However thats not all. At all time feel free to have fun and work on
>>>>>> anything you like on Camel. There is still time for small improvements
>>>>>> etc. But bigger stuff we should really defer to the next release.
>>>>>>
>>>>>>
>>>>>> On Wed, Apr 12, 2017 at 3:35 PM, Antonin Stefanutti
>>>>>> <an...@stefanutti.fr> wrote:
>>>>>>>
>>>>>>>> On 12 Apr 2017, at 15:22, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> Just a heads up that we plan to cut the RC for Camel 2.19 next week.
>>>>>>>>
>>>>>>>> So we are closing down on the last tickets, bugs, features etc to get
>>>>>>>> the code base in shape.
>>>>>>>>
>>>>>>>> The JIRA has 9 tickets
>>>>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved
>>>>>>>>
>>>>>>>> But you are of course welcome to work on other tickets etc but just
>>>>>>>> mind any big functionality is likely better to wait for next release.
>>>>>>>>
>>>>>>>> There is however the expected transaction stuff for CDI as a PR in the
>>>>>>>> works, and also a new iot component
>>>>>>>> https://github.com/apache/camel/pulls
>>>>>>>
>>>>>>> The CDI transaction support PR should be merged by end of week.
>>>>>>>
>>>>>>> https://github.com/apache/camel/pull/1390
>>>>>>>
>>>>>>>> We should keep an eye on the CI servers to see how they are and fix
>>>>>>>> any test failures etc. Recently we got them to build and test the OSGi
>>>>>>>> and spring-boot specific tests so we should be able to better keep an
>>>>>>>> eye on this now and in the future.
>>>>>>>> https://builds.apache.org/view/A-D/view/Camel/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, Apr 7, 2017 at 8:45 AM, Gregor Zurowski
>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>> Hi Claus,
>>>>>>>>>
>>>>>>>>> Week 16 works for me.  I will send out another email shortly before
>>>>>>>>> starting to build the RC.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Gregor
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Apr 5, 2017 at 3:08 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>> Hi Gregor
>>>>>>>>>>
>>>>>>>>>> Yeah its April so we should get the 2.19.0 release out the door.
>>>>>>>>>>
>>>>>>>>>> We have just setup a 2.20.0 version in JIRA and folks should start
>>>>>>>>>> moving their tickets to that version if its something that they cannot
>>>>>>>>>> finish in time. Also we should refrain from doing bigger work at this
>>>>>>>>>> time as we should close down on last tickets, bug fixes, and get the
>>>>>>>>>> CI tests in good order, etc.
>>>>>>>>>>
>>>>>>>>>> I will look at the JIRAs later this week and cleanup a bit so we have
>>>>>>>>>> a better overview of what work is yet to be done.
>>>>>>>>>>
>>>>>>>>>> As April has the easter holidays. I wonder what you time schedule looks like?
>>>>>>>>>>
>>>>>>>>>> Maybe if you have time to help with the release after the holidays?
>>>>>>>>>>
>>>>>>>>>> Week 16 and 17 are the last 2 weeks in April after the holidays.
>>>>>>>>>> If we could maybe cut the RC in week 16 then that would be good.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Apr 3, 2017 at 2:14 PM, Gregor Zurowski
>>>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> Are we getting closer to build a 2.19.0 release?  I would volunteer
>>>>>>>>>>> for creating the release, just wanted to check when would be a good
>>>>>>>>>>> time to do so.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Gregor
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Mar 15, 2017 at 9:29 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>>> Hi
>>>>>>>>>>>>
>>>>>>>>>>>> Just wanted to bring up that we are closing in on a good time for
>>>>>>>>>>>> doing a new release.
>>>>>>>>>>>>
>>>>>>>>>>>> For example in mid April it would be around 6 months since the last
>>>>>>>>>>>> 2.18.0 release.
>>>>>>>>>>>>
>>>>>>>>>>>> Therefore we should start closing down and fixing bugs, and make sure
>>>>>>>>>>>> the CI servers and tests are in good shape.
>>>>>>>>>>>> This morning we have fixed a number of recent test failures and are
>>>>>>>>>>>> down to only 1 test failure now.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Jan 16, 2017 at 10:28 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>>>> Hi
>>>>>>>>>>>>>
>>>>>>>>>>>>> There is a bunch of stuff which we can/should have on the roadmap to
>>>>>>>>>>>>> complete for the Camel 2.19 release.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Here is on top of my head
>>>>>>>>>>>>>
>>>>>>>>>>>>> 1)
>>>>>>>>>>>>> Finish migrating the wiki documentation to adoc files. I think its
>>>>>>>>>>>>> most of the EIP patterns that are missing. There is a basic list of
>>>>>>>>>>>>> EIPs here: https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2)
>>>>>>>>>>>>> Generate documentation and website. Maybe documentation first and then
>>>>>>>>>>>>> we come up with a modern website later - when we have a new logo as
>>>>>>>>>>>>> well.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 3)
>>>>>>>>>>>>> Mark more stuff to @deprecate so we dont drag them into Camel 3.0.
>>>>>>>>>>>>> This is both components / and other artifacts.
>>>>>>>>>>>>> And as well the camel-core APIs where there is maybe more we can deprecate.
>>>>>>>>>>>>> For example the old stuff that was created prior to the component docs
>>>>>>>>>>>>> we do now with the apt plugin at build time instead of this old code
>>>>>>>>>>>>> with runtime that dont really pan out anyway.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 4)
>>>>>>>>>>>>> Move spring-boot starters into the platforms folder. There is a ticket
>>>>>>>>>>>>> about this.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 5)
>>>>>>>>>>>>> More improvements to spring boot auto configuration. We have a bunch
>>>>>>>>>>>>> of tickets on that.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 6)
>>>>>>>>>>>>> Look at the health check API and see if there is something we can get
>>>>>>>>>>>>> started on.
>>>>>>>>>>>>> Possible some API to integrate with spring boot actuators (when using
>>>>>>>>>>>>> SB) and allow each component to provide their own checks so they can
>>>>>>>>>>>>> be implemented ad-hoc. There is a ticket about this.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 7)
>>>>>>>>>>>>> Possible some more teaks to camel-catalog based on feedback from IDEA
>>>>>>>>>>>>> plugin and the maven validate goal.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 8)
>>>>>>>>>>>>> That CDI JEE transaction PR on github.
>>>>>>>>>>>>> Ideally we would have had a transaction API in camel-core and then one
>>>>>>>>>>>>> impl for camel-spring, and then another for camel-cdi-jee. But that
>>>>>>>>>>>>> may require too much work.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 9)
>>>>>>>>>>>>> Work on the Java 8 DSL such as get more community feedback, and then
>>>>>>>>>>>>> resolve the TODOs with the documentation updates and look into other
>>>>>>>>>>>>> areas where the API can benefit from Java 8 lambdas and whatnot. I
>>>>>>>>>>>>> dont think we have a ticket about this.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 10)
>>>>>>>>>>>>> Karaf users may want to improve/finish up the camel-test-karaf module
>>>>>>>>>>>>> so its more usable and end users can use it to test integration tests
>>>>>>>>>>>>> with Camel and Karaf.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 11)
>>>>>>>>>>>>> Introduce Camel Connectors (more about this later)
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Anything else?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Claus Ibsen
>>>>>>>>>>>>> -----------------
>>>>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Claus Ibsen
>>>>>>>>>>>> -----------------
>>>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Claus Ibsen
>>>>>>>>>> -----------------
>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Claus Ibsen
>>>>>>>> -----------------
>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> http://davsclaus.com @davsclaus
>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

Okay we are looking in good shape.

We are waiting for the new 1.5.3 release of spring boot. They have
just released 1.4.6 today.

The CI server are blue/green for the last number of builds.
But lets keep an eye on them. Ideally we should have java 9 be able to
build the source code.





On Wed, Apr 19, 2017 at 2:21 PM, Luca Burgazzoli <lb...@gmail.com> wrote:
> Hi,
>
> I have one little refactoring (rename LoadBalancer in camel cloud
> package to avoid confusion with LoadBalancer processor) and a little
> doc update that I'm trying to make by end of day.
>
>
>
> ---
> Luca Burgazzoli
>
>
> On Wed, Apr 19, 2017 at 1:39 PM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi
>>
>> So the @Generated and Java 9 ought to be fixed now.
>>
>> There is a new version of Spring Boot 1.5.3 on the way. It may be
>> beneficial to wait for that to be released so we are running on
>> latest.
>>
>> On Wed, Apr 19, 2017 at 9:54 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>> Hi
>>>
>>> Okay so there is some last minute issues with the @Generated
>>> annotations we need to look into
>>> https://issues.apache.org/jira/browse/CAMEL-11165
>>>
>>> And an unforseen effect on java 9 builds
>>> https://issues.apache.org/jira/browse/CAMEL-11166
>>>
>>> The full test is passing now. And the Spring Boot and Karaf tests has
>>> also passed but failed recently due some maven download error or some
>>> other weird error. So lets kick new builds when we get the 2 tickets
>>> resolved above.
>>>
>>>
>>>
>>>
>>> On Tue, Apr 18, 2017 at 9:45 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>> Hi
>>>>
>>>> Things start to look good. There is a itest that fails with spring
>>>> boot which we need to look at and get fixed
>>>> https://issues.apache.org/jira/browse/CAMEL-11154
>>>>
>>>> The other tests was all passing recently and they ought to become blue
>>>> again. But lets keep an eye on them:
>>>> https://builds.apache.org/view/A-D/view/Camel/
>>>>
>>>>
>>>> On Thu, Apr 13, 2017 at 1:50 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>> Hi
>>>>>
>>>>> Thanks Antonin that sounds great.
>>>>>
>>>>> The JIRA tickets are down to 3
>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved
>>>>>
>>>>> We have recently fixed up the missing component docs and fixed broken
>>>>> links from browsing on github.
>>>>>
>>>>> We should keep an eye on the CI servers and output from the
>>>>> camel-catalog report, to see if it reports more missing stuff.
>>>>> It currently has a false positive on some missing docs for some of the
>>>>> test components. I will try to fix this later today.
>>>>>
>>>>> However thats not all. At all time feel free to have fun and work on
>>>>> anything you like on Camel. There is still time for small improvements
>>>>> etc. But bigger stuff we should really defer to the next release.
>>>>>
>>>>>
>>>>> On Wed, Apr 12, 2017 at 3:35 PM, Antonin Stefanutti
>>>>> <an...@stefanutti.fr> wrote:
>>>>>>
>>>>>>> On 12 Apr 2017, at 15:22, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> Just a heads up that we plan to cut the RC for Camel 2.19 next week.
>>>>>>>
>>>>>>> So we are closing down on the last tickets, bugs, features etc to get
>>>>>>> the code base in shape.
>>>>>>>
>>>>>>> The JIRA has 9 tickets
>>>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved
>>>>>>>
>>>>>>> But you are of course welcome to work on other tickets etc but just
>>>>>>> mind any big functionality is likely better to wait for next release.
>>>>>>>
>>>>>>> There is however the expected transaction stuff for CDI as a PR in the
>>>>>>> works, and also a new iot component
>>>>>>> https://github.com/apache/camel/pulls
>>>>>>
>>>>>> The CDI transaction support PR should be merged by end of week.
>>>>>>
>>>>>> https://github.com/apache/camel/pull/1390
>>>>>>
>>>>>>> We should keep an eye on the CI servers to see how they are and fix
>>>>>>> any test failures etc. Recently we got them to build and test the OSGi
>>>>>>> and spring-boot specific tests so we should be able to better keep an
>>>>>>> eye on this now and in the future.
>>>>>>> https://builds.apache.org/view/A-D/view/Camel/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Apr 7, 2017 at 8:45 AM, Gregor Zurowski
>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>> Hi Claus,
>>>>>>>>
>>>>>>>> Week 16 works for me.  I will send out another email shortly before
>>>>>>>> starting to build the RC.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Gregor
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Apr 5, 2017 at 3:08 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>> Hi Gregor
>>>>>>>>>
>>>>>>>>> Yeah its April so we should get the 2.19.0 release out the door.
>>>>>>>>>
>>>>>>>>> We have just setup a 2.20.0 version in JIRA and folks should start
>>>>>>>>> moving their tickets to that version if its something that they cannot
>>>>>>>>> finish in time. Also we should refrain from doing bigger work at this
>>>>>>>>> time as we should close down on last tickets, bug fixes, and get the
>>>>>>>>> CI tests in good order, etc.
>>>>>>>>>
>>>>>>>>> I will look at the JIRAs later this week and cleanup a bit so we have
>>>>>>>>> a better overview of what work is yet to be done.
>>>>>>>>>
>>>>>>>>> As April has the easter holidays. I wonder what you time schedule looks like?
>>>>>>>>>
>>>>>>>>> Maybe if you have time to help with the release after the holidays?
>>>>>>>>>
>>>>>>>>> Week 16 and 17 are the last 2 weeks in April after the holidays.
>>>>>>>>> If we could maybe cut the RC in week 16 then that would be good.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Apr 3, 2017 at 2:14 PM, Gregor Zurowski
>>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> Are we getting closer to build a 2.19.0 release?  I would volunteer
>>>>>>>>>> for creating the release, just wanted to check when would be a good
>>>>>>>>>> time to do so.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Gregor
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Mar 15, 2017 at 9:29 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>> Hi
>>>>>>>>>>>
>>>>>>>>>>> Just wanted to bring up that we are closing in on a good time for
>>>>>>>>>>> doing a new release.
>>>>>>>>>>>
>>>>>>>>>>> For example in mid April it would be around 6 months since the last
>>>>>>>>>>> 2.18.0 release.
>>>>>>>>>>>
>>>>>>>>>>> Therefore we should start closing down and fixing bugs, and make sure
>>>>>>>>>>> the CI servers and tests are in good shape.
>>>>>>>>>>> This morning we have fixed a number of recent test failures and are
>>>>>>>>>>> down to only 1 test failure now.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Jan 16, 2017 at 10:28 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>>> Hi
>>>>>>>>>>>>
>>>>>>>>>>>> There is a bunch of stuff which we can/should have on the roadmap to
>>>>>>>>>>>> complete for the Camel 2.19 release.
>>>>>>>>>>>>
>>>>>>>>>>>> Here is on top of my head
>>>>>>>>>>>>
>>>>>>>>>>>> 1)
>>>>>>>>>>>> Finish migrating the wiki documentation to adoc files. I think its
>>>>>>>>>>>> most of the EIP patterns that are missing. There is a basic list of
>>>>>>>>>>>> EIPs here: https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc
>>>>>>>>>>>>
>>>>>>>>>>>> 2)
>>>>>>>>>>>> Generate documentation and website. Maybe documentation first and then
>>>>>>>>>>>> we come up with a modern website later - when we have a new logo as
>>>>>>>>>>>> well.
>>>>>>>>>>>>
>>>>>>>>>>>> 3)
>>>>>>>>>>>> Mark more stuff to @deprecate so we dont drag them into Camel 3.0.
>>>>>>>>>>>> This is both components / and other artifacts.
>>>>>>>>>>>> And as well the camel-core APIs where there is maybe more we can deprecate.
>>>>>>>>>>>> For example the old stuff that was created prior to the component docs
>>>>>>>>>>>> we do now with the apt plugin at build time instead of this old code
>>>>>>>>>>>> with runtime that dont really pan out anyway.
>>>>>>>>>>>>
>>>>>>>>>>>> 4)
>>>>>>>>>>>> Move spring-boot starters into the platforms folder. There is a ticket
>>>>>>>>>>>> about this.
>>>>>>>>>>>>
>>>>>>>>>>>> 5)
>>>>>>>>>>>> More improvements to spring boot auto configuration. We have a bunch
>>>>>>>>>>>> of tickets on that.
>>>>>>>>>>>>
>>>>>>>>>>>> 6)
>>>>>>>>>>>> Look at the health check API and see if there is something we can get
>>>>>>>>>>>> started on.
>>>>>>>>>>>> Possible some API to integrate with spring boot actuators (when using
>>>>>>>>>>>> SB) and allow each component to provide their own checks so they can
>>>>>>>>>>>> be implemented ad-hoc. There is a ticket about this.
>>>>>>>>>>>>
>>>>>>>>>>>> 7)
>>>>>>>>>>>> Possible some more teaks to camel-catalog based on feedback from IDEA
>>>>>>>>>>>> plugin and the maven validate goal.
>>>>>>>>>>>>
>>>>>>>>>>>> 8)
>>>>>>>>>>>> That CDI JEE transaction PR on github.
>>>>>>>>>>>> Ideally we would have had a transaction API in camel-core and then one
>>>>>>>>>>>> impl for camel-spring, and then another for camel-cdi-jee. But that
>>>>>>>>>>>> may require too much work.
>>>>>>>>>>>>
>>>>>>>>>>>> 9)
>>>>>>>>>>>> Work on the Java 8 DSL such as get more community feedback, and then
>>>>>>>>>>>> resolve the TODOs with the documentation updates and look into other
>>>>>>>>>>>> areas where the API can benefit from Java 8 lambdas and whatnot. I
>>>>>>>>>>>> dont think we have a ticket about this.
>>>>>>>>>>>>
>>>>>>>>>>>> 10)
>>>>>>>>>>>> Karaf users may want to improve/finish up the camel-test-karaf module
>>>>>>>>>>>> so its more usable and end users can use it to test integration tests
>>>>>>>>>>>> with Camel and Karaf.
>>>>>>>>>>>>
>>>>>>>>>>>> 11)
>>>>>>>>>>>> Introduce Camel Connectors (more about this later)
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Anything else?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Claus Ibsen
>>>>>>>>>>>> -----------------
>>>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Claus Ibsen
>>>>>>>>>>> -----------------
>>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Claus Ibsen
>>>>>>>>> -----------------
>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Claus Ibsen
>>>>>>> -----------------
>>>>>>> http://davsclaus.com @davsclaus
>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Luca Burgazzoli <lb...@gmail.com>.
Hi,

I have one little refactoring (rename LoadBalancer in camel cloud
package to avoid confusion with LoadBalancer processor) and a little
doc update that I'm trying to make by end of day.



---
Luca Burgazzoli


On Wed, Apr 19, 2017 at 1:39 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> So the @Generated and Java 9 ought to be fixed now.
>
> There is a new version of Spring Boot 1.5.3 on the way. It may be
> beneficial to wait for that to be released so we are running on
> latest.
>
> On Wed, Apr 19, 2017 at 9:54 AM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi
>>
>> Okay so there is some last minute issues with the @Generated
>> annotations we need to look into
>> https://issues.apache.org/jira/browse/CAMEL-11165
>>
>> And an unforseen effect on java 9 builds
>> https://issues.apache.org/jira/browse/CAMEL-11166
>>
>> The full test is passing now. And the Spring Boot and Karaf tests has
>> also passed but failed recently due some maven download error or some
>> other weird error. So lets kick new builds when we get the 2 tickets
>> resolved above.
>>
>>
>>
>>
>> On Tue, Apr 18, 2017 at 9:45 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>> Hi
>>>
>>> Things start to look good. There is a itest that fails with spring
>>> boot which we need to look at and get fixed
>>> https://issues.apache.org/jira/browse/CAMEL-11154
>>>
>>> The other tests was all passing recently and they ought to become blue
>>> again. But lets keep an eye on them:
>>> https://builds.apache.org/view/A-D/view/Camel/
>>>
>>>
>>> On Thu, Apr 13, 2017 at 1:50 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>> Hi
>>>>
>>>> Thanks Antonin that sounds great.
>>>>
>>>> The JIRA tickets are down to 3
>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved
>>>>
>>>> We have recently fixed up the missing component docs and fixed broken
>>>> links from browsing on github.
>>>>
>>>> We should keep an eye on the CI servers and output from the
>>>> camel-catalog report, to see if it reports more missing stuff.
>>>> It currently has a false positive on some missing docs for some of the
>>>> test components. I will try to fix this later today.
>>>>
>>>> However thats not all. At all time feel free to have fun and work on
>>>> anything you like on Camel. There is still time for small improvements
>>>> etc. But bigger stuff we should really defer to the next release.
>>>>
>>>>
>>>> On Wed, Apr 12, 2017 at 3:35 PM, Antonin Stefanutti
>>>> <an...@stefanutti.fr> wrote:
>>>>>
>>>>>> On 12 Apr 2017, at 15:22, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>> Just a heads up that we plan to cut the RC for Camel 2.19 next week.
>>>>>>
>>>>>> So we are closing down on the last tickets, bugs, features etc to get
>>>>>> the code base in shape.
>>>>>>
>>>>>> The JIRA has 9 tickets
>>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved
>>>>>>
>>>>>> But you are of course welcome to work on other tickets etc but just
>>>>>> mind any big functionality is likely better to wait for next release.
>>>>>>
>>>>>> There is however the expected transaction stuff for CDI as a PR in the
>>>>>> works, and also a new iot component
>>>>>> https://github.com/apache/camel/pulls
>>>>>
>>>>> The CDI transaction support PR should be merged by end of week.
>>>>>
>>>>> https://github.com/apache/camel/pull/1390
>>>>>
>>>>>> We should keep an eye on the CI servers to see how they are and fix
>>>>>> any test failures etc. Recently we got them to build and test the OSGi
>>>>>> and spring-boot specific tests so we should be able to better keep an
>>>>>> eye on this now and in the future.
>>>>>> https://builds.apache.org/view/A-D/view/Camel/
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Apr 7, 2017 at 8:45 AM, Gregor Zurowski
>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>> Hi Claus,
>>>>>>>
>>>>>>> Week 16 works for me.  I will send out another email shortly before
>>>>>>> starting to build the RC.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Gregor
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Apr 5, 2017 at 3:08 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>> Hi Gregor
>>>>>>>>
>>>>>>>> Yeah its April so we should get the 2.19.0 release out the door.
>>>>>>>>
>>>>>>>> We have just setup a 2.20.0 version in JIRA and folks should start
>>>>>>>> moving their tickets to that version if its something that they cannot
>>>>>>>> finish in time. Also we should refrain from doing bigger work at this
>>>>>>>> time as we should close down on last tickets, bug fixes, and get the
>>>>>>>> CI tests in good order, etc.
>>>>>>>>
>>>>>>>> I will look at the JIRAs later this week and cleanup a bit so we have
>>>>>>>> a better overview of what work is yet to be done.
>>>>>>>>
>>>>>>>> As April has the easter holidays. I wonder what you time schedule looks like?
>>>>>>>>
>>>>>>>> Maybe if you have time to help with the release after the holidays?
>>>>>>>>
>>>>>>>> Week 16 and 17 are the last 2 weeks in April after the holidays.
>>>>>>>> If we could maybe cut the RC in week 16 then that would be good.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Apr 3, 2017 at 2:14 PM, Gregor Zurowski
>>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> Are we getting closer to build a 2.19.0 release?  I would volunteer
>>>>>>>>> for creating the release, just wanted to check when would be a good
>>>>>>>>> time to do so.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Gregor
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Mar 15, 2017 at 9:29 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>> Hi
>>>>>>>>>>
>>>>>>>>>> Just wanted to bring up that we are closing in on a good time for
>>>>>>>>>> doing a new release.
>>>>>>>>>>
>>>>>>>>>> For example in mid April it would be around 6 months since the last
>>>>>>>>>> 2.18.0 release.
>>>>>>>>>>
>>>>>>>>>> Therefore we should start closing down and fixing bugs, and make sure
>>>>>>>>>> the CI servers and tests are in good shape.
>>>>>>>>>> This morning we have fixed a number of recent test failures and are
>>>>>>>>>> down to only 1 test failure now.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Jan 16, 2017 at 10:28 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>>> Hi
>>>>>>>>>>>
>>>>>>>>>>> There is a bunch of stuff which we can/should have on the roadmap to
>>>>>>>>>>> complete for the Camel 2.19 release.
>>>>>>>>>>>
>>>>>>>>>>> Here is on top of my head
>>>>>>>>>>>
>>>>>>>>>>> 1)
>>>>>>>>>>> Finish migrating the wiki documentation to adoc files. I think its
>>>>>>>>>>> most of the EIP patterns that are missing. There is a basic list of
>>>>>>>>>>> EIPs here: https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc
>>>>>>>>>>>
>>>>>>>>>>> 2)
>>>>>>>>>>> Generate documentation and website. Maybe documentation first and then
>>>>>>>>>>> we come up with a modern website later - when we have a new logo as
>>>>>>>>>>> well.
>>>>>>>>>>>
>>>>>>>>>>> 3)
>>>>>>>>>>> Mark more stuff to @deprecate so we dont drag them into Camel 3.0.
>>>>>>>>>>> This is both components / and other artifacts.
>>>>>>>>>>> And as well the camel-core APIs where there is maybe more we can deprecate.
>>>>>>>>>>> For example the old stuff that was created prior to the component docs
>>>>>>>>>>> we do now with the apt plugin at build time instead of this old code
>>>>>>>>>>> with runtime that dont really pan out anyway.
>>>>>>>>>>>
>>>>>>>>>>> 4)
>>>>>>>>>>> Move spring-boot starters into the platforms folder. There is a ticket
>>>>>>>>>>> about this.
>>>>>>>>>>>
>>>>>>>>>>> 5)
>>>>>>>>>>> More improvements to spring boot auto configuration. We have a bunch
>>>>>>>>>>> of tickets on that.
>>>>>>>>>>>
>>>>>>>>>>> 6)
>>>>>>>>>>> Look at the health check API and see if there is something we can get
>>>>>>>>>>> started on.
>>>>>>>>>>> Possible some API to integrate with spring boot actuators (when using
>>>>>>>>>>> SB) and allow each component to provide their own checks so they can
>>>>>>>>>>> be implemented ad-hoc. There is a ticket about this.
>>>>>>>>>>>
>>>>>>>>>>> 7)
>>>>>>>>>>> Possible some more teaks to camel-catalog based on feedback from IDEA
>>>>>>>>>>> plugin and the maven validate goal.
>>>>>>>>>>>
>>>>>>>>>>> 8)
>>>>>>>>>>> That CDI JEE transaction PR on github.
>>>>>>>>>>> Ideally we would have had a transaction API in camel-core and then one
>>>>>>>>>>> impl for camel-spring, and then another for camel-cdi-jee. But that
>>>>>>>>>>> may require too much work.
>>>>>>>>>>>
>>>>>>>>>>> 9)
>>>>>>>>>>> Work on the Java 8 DSL such as get more community feedback, and then
>>>>>>>>>>> resolve the TODOs with the documentation updates and look into other
>>>>>>>>>>> areas where the API can benefit from Java 8 lambdas and whatnot. I
>>>>>>>>>>> dont think we have a ticket about this.
>>>>>>>>>>>
>>>>>>>>>>> 10)
>>>>>>>>>>> Karaf users may want to improve/finish up the camel-test-karaf module
>>>>>>>>>>> so its more usable and end users can use it to test integration tests
>>>>>>>>>>> with Camel and Karaf.
>>>>>>>>>>>
>>>>>>>>>>> 11)
>>>>>>>>>>> Introduce Camel Connectors (more about this later)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Anything else?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Claus Ibsen
>>>>>>>>>>> -----------------
>>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Claus Ibsen
>>>>>>>>>> -----------------
>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Claus Ibsen
>>>>>>>> -----------------
>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> http://davsclaus.com @davsclaus
>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

So the @Generated and Java 9 ought to be fixed now.

There is a new version of Spring Boot 1.5.3 on the way. It may be
beneficial to wait for that to be released so we are running on
latest.

On Wed, Apr 19, 2017 at 9:54 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> Okay so there is some last minute issues with the @Generated
> annotations we need to look into
> https://issues.apache.org/jira/browse/CAMEL-11165
>
> And an unforseen effect on java 9 builds
> https://issues.apache.org/jira/browse/CAMEL-11166
>
> The full test is passing now. And the Spring Boot and Karaf tests has
> also passed but failed recently due some maven download error or some
> other weird error. So lets kick new builds when we get the 2 tickets
> resolved above.
>
>
>
>
> On Tue, Apr 18, 2017 at 9:45 AM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi
>>
>> Things start to look good. There is a itest that fails with spring
>> boot which we need to look at and get fixed
>> https://issues.apache.org/jira/browse/CAMEL-11154
>>
>> The other tests was all passing recently and they ought to become blue
>> again. But lets keep an eye on them:
>> https://builds.apache.org/view/A-D/view/Camel/
>>
>>
>> On Thu, Apr 13, 2017 at 1:50 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>> Hi
>>>
>>> Thanks Antonin that sounds great.
>>>
>>> The JIRA tickets are down to 3
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved
>>>
>>> We have recently fixed up the missing component docs and fixed broken
>>> links from browsing on github.
>>>
>>> We should keep an eye on the CI servers and output from the
>>> camel-catalog report, to see if it reports more missing stuff.
>>> It currently has a false positive on some missing docs for some of the
>>> test components. I will try to fix this later today.
>>>
>>> However thats not all. At all time feel free to have fun and work on
>>> anything you like on Camel. There is still time for small improvements
>>> etc. But bigger stuff we should really defer to the next release.
>>>
>>>
>>> On Wed, Apr 12, 2017 at 3:35 PM, Antonin Stefanutti
>>> <an...@stefanutti.fr> wrote:
>>>>
>>>>> On 12 Apr 2017, at 15:22, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> Just a heads up that we plan to cut the RC for Camel 2.19 next week.
>>>>>
>>>>> So we are closing down on the last tickets, bugs, features etc to get
>>>>> the code base in shape.
>>>>>
>>>>> The JIRA has 9 tickets
>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved
>>>>>
>>>>> But you are of course welcome to work on other tickets etc but just
>>>>> mind any big functionality is likely better to wait for next release.
>>>>>
>>>>> There is however the expected transaction stuff for CDI as a PR in the
>>>>> works, and also a new iot component
>>>>> https://github.com/apache/camel/pulls
>>>>
>>>> The CDI transaction support PR should be merged by end of week.
>>>>
>>>> https://github.com/apache/camel/pull/1390
>>>>
>>>>> We should keep an eye on the CI servers to see how they are and fix
>>>>> any test failures etc. Recently we got them to build and test the OSGi
>>>>> and spring-boot specific tests so we should be able to better keep an
>>>>> eye on this now and in the future.
>>>>> https://builds.apache.org/view/A-D/view/Camel/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Apr 7, 2017 at 8:45 AM, Gregor Zurowski
>>>>> <gr...@list.zurowski.org> wrote:
>>>>>> Hi Claus,
>>>>>>
>>>>>> Week 16 works for me.  I will send out another email shortly before
>>>>>> starting to build the RC.
>>>>>>
>>>>>> Thanks,
>>>>>> Gregor
>>>>>>
>>>>>>
>>>>>> On Wed, Apr 5, 2017 at 3:08 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>> Hi Gregor
>>>>>>>
>>>>>>> Yeah its April so we should get the 2.19.0 release out the door.
>>>>>>>
>>>>>>> We have just setup a 2.20.0 version in JIRA and folks should start
>>>>>>> moving their tickets to that version if its something that they cannot
>>>>>>> finish in time. Also we should refrain from doing bigger work at this
>>>>>>> time as we should close down on last tickets, bug fixes, and get the
>>>>>>> CI tests in good order, etc.
>>>>>>>
>>>>>>> I will look at the JIRAs later this week and cleanup a bit so we have
>>>>>>> a better overview of what work is yet to be done.
>>>>>>>
>>>>>>> As April has the easter holidays. I wonder what you time schedule looks like?
>>>>>>>
>>>>>>> Maybe if you have time to help with the release after the holidays?
>>>>>>>
>>>>>>> Week 16 and 17 are the last 2 weeks in April after the holidays.
>>>>>>> If we could maybe cut the RC in week 16 then that would be good.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Apr 3, 2017 at 2:14 PM, Gregor Zurowski
>>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> Are we getting closer to build a 2.19.0 release?  I would volunteer
>>>>>>>> for creating the release, just wanted to check when would be a good
>>>>>>>> time to do so.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Gregor
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Mar 15, 2017 at 9:29 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>> Hi
>>>>>>>>>
>>>>>>>>> Just wanted to bring up that we are closing in on a good time for
>>>>>>>>> doing a new release.
>>>>>>>>>
>>>>>>>>> For example in mid April it would be around 6 months since the last
>>>>>>>>> 2.18.0 release.
>>>>>>>>>
>>>>>>>>> Therefore we should start closing down and fixing bugs, and make sure
>>>>>>>>> the CI servers and tests are in good shape.
>>>>>>>>> This morning we have fixed a number of recent test failures and are
>>>>>>>>> down to only 1 test failure now.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Jan 16, 2017 at 10:28 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>>> Hi
>>>>>>>>>>
>>>>>>>>>> There is a bunch of stuff which we can/should have on the roadmap to
>>>>>>>>>> complete for the Camel 2.19 release.
>>>>>>>>>>
>>>>>>>>>> Here is on top of my head
>>>>>>>>>>
>>>>>>>>>> 1)
>>>>>>>>>> Finish migrating the wiki documentation to adoc files. I think its
>>>>>>>>>> most of the EIP patterns that are missing. There is a basic list of
>>>>>>>>>> EIPs here: https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc
>>>>>>>>>>
>>>>>>>>>> 2)
>>>>>>>>>> Generate documentation and website. Maybe documentation first and then
>>>>>>>>>> we come up with a modern website later - when we have a new logo as
>>>>>>>>>> well.
>>>>>>>>>>
>>>>>>>>>> 3)
>>>>>>>>>> Mark more stuff to @deprecate so we dont drag them into Camel 3.0.
>>>>>>>>>> This is both components / and other artifacts.
>>>>>>>>>> And as well the camel-core APIs where there is maybe more we can deprecate.
>>>>>>>>>> For example the old stuff that was created prior to the component docs
>>>>>>>>>> we do now with the apt plugin at build time instead of this old code
>>>>>>>>>> with runtime that dont really pan out anyway.
>>>>>>>>>>
>>>>>>>>>> 4)
>>>>>>>>>> Move spring-boot starters into the platforms folder. There is a ticket
>>>>>>>>>> about this.
>>>>>>>>>>
>>>>>>>>>> 5)
>>>>>>>>>> More improvements to spring boot auto configuration. We have a bunch
>>>>>>>>>> of tickets on that.
>>>>>>>>>>
>>>>>>>>>> 6)
>>>>>>>>>> Look at the health check API and see if there is something we can get
>>>>>>>>>> started on.
>>>>>>>>>> Possible some API to integrate with spring boot actuators (when using
>>>>>>>>>> SB) and allow each component to provide their own checks so they can
>>>>>>>>>> be implemented ad-hoc. There is a ticket about this.
>>>>>>>>>>
>>>>>>>>>> 7)
>>>>>>>>>> Possible some more teaks to camel-catalog based on feedback from IDEA
>>>>>>>>>> plugin and the maven validate goal.
>>>>>>>>>>
>>>>>>>>>> 8)
>>>>>>>>>> That CDI JEE transaction PR on github.
>>>>>>>>>> Ideally we would have had a transaction API in camel-core and then one
>>>>>>>>>> impl for camel-spring, and then another for camel-cdi-jee. But that
>>>>>>>>>> may require too much work.
>>>>>>>>>>
>>>>>>>>>> 9)
>>>>>>>>>> Work on the Java 8 DSL such as get more community feedback, and then
>>>>>>>>>> resolve the TODOs with the documentation updates and look into other
>>>>>>>>>> areas where the API can benefit from Java 8 lambdas and whatnot. I
>>>>>>>>>> dont think we have a ticket about this.
>>>>>>>>>>
>>>>>>>>>> 10)
>>>>>>>>>> Karaf users may want to improve/finish up the camel-test-karaf module
>>>>>>>>>> so its more usable and end users can use it to test integration tests
>>>>>>>>>> with Camel and Karaf.
>>>>>>>>>>
>>>>>>>>>> 11)
>>>>>>>>>> Introduce Camel Connectors (more about this later)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Anything else?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Claus Ibsen
>>>>>>>>>> -----------------
>>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Claus Ibsen
>>>>>>>>> -----------------
>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Claus Ibsen
>>>>>>> -----------------
>>>>>>> http://davsclaus.com @davsclaus
>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

Okay so there is some last minute issues with the @Generated
annotations we need to look into
https://issues.apache.org/jira/browse/CAMEL-11165

And an unforseen effect on java 9 builds
https://issues.apache.org/jira/browse/CAMEL-11166

The full test is passing now. And the Spring Boot and Karaf tests has
also passed but failed recently due some maven download error or some
other weird error. So lets kick new builds when we get the 2 tickets
resolved above.




On Tue, Apr 18, 2017 at 9:45 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> Things start to look good. There is a itest that fails with spring
> boot which we need to look at and get fixed
> https://issues.apache.org/jira/browse/CAMEL-11154
>
> The other tests was all passing recently and they ought to become blue
> again. But lets keep an eye on them:
> https://builds.apache.org/view/A-D/view/Camel/
>
>
> On Thu, Apr 13, 2017 at 1:50 PM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi
>>
>> Thanks Antonin that sounds great.
>>
>> The JIRA tickets are down to 3
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved
>>
>> We have recently fixed up the missing component docs and fixed broken
>> links from browsing on github.
>>
>> We should keep an eye on the CI servers and output from the
>> camel-catalog report, to see if it reports more missing stuff.
>> It currently has a false positive on some missing docs for some of the
>> test components. I will try to fix this later today.
>>
>> However thats not all. At all time feel free to have fun and work on
>> anything you like on Camel. There is still time for small improvements
>> etc. But bigger stuff we should really defer to the next release.
>>
>>
>> On Wed, Apr 12, 2017 at 3:35 PM, Antonin Stefanutti
>> <an...@stefanutti.fr> wrote:
>>>
>>>> On 12 Apr 2017, at 15:22, Claus Ibsen <cl...@gmail.com> wrote:
>>>>
>>>> Hi
>>>>
>>>> Just a heads up that we plan to cut the RC for Camel 2.19 next week.
>>>>
>>>> So we are closing down on the last tickets, bugs, features etc to get
>>>> the code base in shape.
>>>>
>>>> The JIRA has 9 tickets
>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved
>>>>
>>>> But you are of course welcome to work on other tickets etc but just
>>>> mind any big functionality is likely better to wait for next release.
>>>>
>>>> There is however the expected transaction stuff for CDI as a PR in the
>>>> works, and also a new iot component
>>>> https://github.com/apache/camel/pulls
>>>
>>> The CDI transaction support PR should be merged by end of week.
>>>
>>> https://github.com/apache/camel/pull/1390
>>>
>>>> We should keep an eye on the CI servers to see how they are and fix
>>>> any test failures etc. Recently we got them to build and test the OSGi
>>>> and spring-boot specific tests so we should be able to better keep an
>>>> eye on this now and in the future.
>>>> https://builds.apache.org/view/A-D/view/Camel/
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Fri, Apr 7, 2017 at 8:45 AM, Gregor Zurowski
>>>> <gr...@list.zurowski.org> wrote:
>>>>> Hi Claus,
>>>>>
>>>>> Week 16 works for me.  I will send out another email shortly before
>>>>> starting to build the RC.
>>>>>
>>>>> Thanks,
>>>>> Gregor
>>>>>
>>>>>
>>>>> On Wed, Apr 5, 2017 at 3:08 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>> Hi Gregor
>>>>>>
>>>>>> Yeah its April so we should get the 2.19.0 release out the door.
>>>>>>
>>>>>> We have just setup a 2.20.0 version in JIRA and folks should start
>>>>>> moving their tickets to that version if its something that they cannot
>>>>>> finish in time. Also we should refrain from doing bigger work at this
>>>>>> time as we should close down on last tickets, bug fixes, and get the
>>>>>> CI tests in good order, etc.
>>>>>>
>>>>>> I will look at the JIRAs later this week and cleanup a bit so we have
>>>>>> a better overview of what work is yet to be done.
>>>>>>
>>>>>> As April has the easter holidays. I wonder what you time schedule looks like?
>>>>>>
>>>>>> Maybe if you have time to help with the release after the holidays?
>>>>>>
>>>>>> Week 16 and 17 are the last 2 weeks in April after the holidays.
>>>>>> If we could maybe cut the RC in week 16 then that would be good.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Apr 3, 2017 at 2:14 PM, Gregor Zurowski
>>>>>> <gr...@list.zurowski.org> wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> Are we getting closer to build a 2.19.0 release?  I would volunteer
>>>>>>> for creating the release, just wanted to check when would be a good
>>>>>>> time to do so.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Gregor
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Mar 15, 2017 at 9:29 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> Just wanted to bring up that we are closing in on a good time for
>>>>>>>> doing a new release.
>>>>>>>>
>>>>>>>> For example in mid April it would be around 6 months since the last
>>>>>>>> 2.18.0 release.
>>>>>>>>
>>>>>>>> Therefore we should start closing down and fixing bugs, and make sure
>>>>>>>> the CI servers and tests are in good shape.
>>>>>>>> This morning we have fixed a number of recent test failures and are
>>>>>>>> down to only 1 test failure now.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jan 16, 2017 at 10:28 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>>> Hi
>>>>>>>>>
>>>>>>>>> There is a bunch of stuff which we can/should have on the roadmap to
>>>>>>>>> complete for the Camel 2.19 release.
>>>>>>>>>
>>>>>>>>> Here is on top of my head
>>>>>>>>>
>>>>>>>>> 1)
>>>>>>>>> Finish migrating the wiki documentation to adoc files. I think its
>>>>>>>>> most of the EIP patterns that are missing. There is a basic list of
>>>>>>>>> EIPs here: https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc
>>>>>>>>>
>>>>>>>>> 2)
>>>>>>>>> Generate documentation and website. Maybe documentation first and then
>>>>>>>>> we come up with a modern website later - when we have a new logo as
>>>>>>>>> well.
>>>>>>>>>
>>>>>>>>> 3)
>>>>>>>>> Mark more stuff to @deprecate so we dont drag them into Camel 3.0.
>>>>>>>>> This is both components / and other artifacts.
>>>>>>>>> And as well the camel-core APIs where there is maybe more we can deprecate.
>>>>>>>>> For example the old stuff that was created prior to the component docs
>>>>>>>>> we do now with the apt plugin at build time instead of this old code
>>>>>>>>> with runtime that dont really pan out anyway.
>>>>>>>>>
>>>>>>>>> 4)
>>>>>>>>> Move spring-boot starters into the platforms folder. There is a ticket
>>>>>>>>> about this.
>>>>>>>>>
>>>>>>>>> 5)
>>>>>>>>> More improvements to spring boot auto configuration. We have a bunch
>>>>>>>>> of tickets on that.
>>>>>>>>>
>>>>>>>>> 6)
>>>>>>>>> Look at the health check API and see if there is something we can get
>>>>>>>>> started on.
>>>>>>>>> Possible some API to integrate with spring boot actuators (when using
>>>>>>>>> SB) and allow each component to provide their own checks so they can
>>>>>>>>> be implemented ad-hoc. There is a ticket about this.
>>>>>>>>>
>>>>>>>>> 7)
>>>>>>>>> Possible some more teaks to camel-catalog based on feedback from IDEA
>>>>>>>>> plugin and the maven validate goal.
>>>>>>>>>
>>>>>>>>> 8)
>>>>>>>>> That CDI JEE transaction PR on github.
>>>>>>>>> Ideally we would have had a transaction API in camel-core and then one
>>>>>>>>> impl for camel-spring, and then another for camel-cdi-jee. But that
>>>>>>>>> may require too much work.
>>>>>>>>>
>>>>>>>>> 9)
>>>>>>>>> Work on the Java 8 DSL such as get more community feedback, and then
>>>>>>>>> resolve the TODOs with the documentation updates and look into other
>>>>>>>>> areas where the API can benefit from Java 8 lambdas and whatnot. I
>>>>>>>>> dont think we have a ticket about this.
>>>>>>>>>
>>>>>>>>> 10)
>>>>>>>>> Karaf users may want to improve/finish up the camel-test-karaf module
>>>>>>>>> so its more usable and end users can use it to test integration tests
>>>>>>>>> with Camel and Karaf.
>>>>>>>>>
>>>>>>>>> 11)
>>>>>>>>> Introduce Camel Connectors (more about this later)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Anything else?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Claus Ibsen
>>>>>>>>> -----------------
>>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Claus Ibsen
>>>>>>>> -----------------
>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> http://davsclaus.com @davsclaus
>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

Things start to look good. There is a itest that fails with spring
boot which we need to look at and get fixed
https://issues.apache.org/jira/browse/CAMEL-11154

The other tests was all passing recently and they ought to become blue
again. But lets keep an eye on them:
https://builds.apache.org/view/A-D/view/Camel/


On Thu, Apr 13, 2017 at 1:50 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> Thanks Antonin that sounds great.
>
> The JIRA tickets are down to 3
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved
>
> We have recently fixed up the missing component docs and fixed broken
> links from browsing on github.
>
> We should keep an eye on the CI servers and output from the
> camel-catalog report, to see if it reports more missing stuff.
> It currently has a false positive on some missing docs for some of the
> test components. I will try to fix this later today.
>
> However thats not all. At all time feel free to have fun and work on
> anything you like on Camel. There is still time for small improvements
> etc. But bigger stuff we should really defer to the next release.
>
>
> On Wed, Apr 12, 2017 at 3:35 PM, Antonin Stefanutti
> <an...@stefanutti.fr> wrote:
>>
>>> On 12 Apr 2017, at 15:22, Claus Ibsen <cl...@gmail.com> wrote:
>>>
>>> Hi
>>>
>>> Just a heads up that we plan to cut the RC for Camel 2.19 next week.
>>>
>>> So we are closing down on the last tickets, bugs, features etc to get
>>> the code base in shape.
>>>
>>> The JIRA has 9 tickets
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved
>>>
>>> But you are of course welcome to work on other tickets etc but just
>>> mind any big functionality is likely better to wait for next release.
>>>
>>> There is however the expected transaction stuff for CDI as a PR in the
>>> works, and also a new iot component
>>> https://github.com/apache/camel/pulls
>>
>> The CDI transaction support PR should be merged by end of week.
>>
>> https://github.com/apache/camel/pull/1390
>>
>>> We should keep an eye on the CI servers to see how they are and fix
>>> any test failures etc. Recently we got them to build and test the OSGi
>>> and spring-boot specific tests so we should be able to better keep an
>>> eye on this now and in the future.
>>> https://builds.apache.org/view/A-D/view/Camel/
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Apr 7, 2017 at 8:45 AM, Gregor Zurowski
>>> <gr...@list.zurowski.org> wrote:
>>>> Hi Claus,
>>>>
>>>> Week 16 works for me.  I will send out another email shortly before
>>>> starting to build the RC.
>>>>
>>>> Thanks,
>>>> Gregor
>>>>
>>>>
>>>> On Wed, Apr 5, 2017 at 3:08 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>> Hi Gregor
>>>>>
>>>>> Yeah its April so we should get the 2.19.0 release out the door.
>>>>>
>>>>> We have just setup a 2.20.0 version in JIRA and folks should start
>>>>> moving their tickets to that version if its something that they cannot
>>>>> finish in time. Also we should refrain from doing bigger work at this
>>>>> time as we should close down on last tickets, bug fixes, and get the
>>>>> CI tests in good order, etc.
>>>>>
>>>>> I will look at the JIRAs later this week and cleanup a bit so we have
>>>>> a better overview of what work is yet to be done.
>>>>>
>>>>> As April has the easter holidays. I wonder what you time schedule looks like?
>>>>>
>>>>> Maybe if you have time to help with the release after the holidays?
>>>>>
>>>>> Week 16 and 17 are the last 2 weeks in April after the holidays.
>>>>> If we could maybe cut the RC in week 16 then that would be good.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Apr 3, 2017 at 2:14 PM, Gregor Zurowski
>>>>> <gr...@list.zurowski.org> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> Are we getting closer to build a 2.19.0 release?  I would volunteer
>>>>>> for creating the release, just wanted to check when would be a good
>>>>>> time to do so.
>>>>>>
>>>>>> Thanks,
>>>>>> Gregor
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 15, 2017 at 9:29 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>> Hi
>>>>>>>
>>>>>>> Just wanted to bring up that we are closing in on a good time for
>>>>>>> doing a new release.
>>>>>>>
>>>>>>> For example in mid April it would be around 6 months since the last
>>>>>>> 2.18.0 release.
>>>>>>>
>>>>>>> Therefore we should start closing down and fixing bugs, and make sure
>>>>>>> the CI servers and tests are in good shape.
>>>>>>> This morning we have fixed a number of recent test failures and are
>>>>>>> down to only 1 test failure now.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jan 16, 2017 at 10:28 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> There is a bunch of stuff which we can/should have on the roadmap to
>>>>>>>> complete for the Camel 2.19 release.
>>>>>>>>
>>>>>>>> Here is on top of my head
>>>>>>>>
>>>>>>>> 1)
>>>>>>>> Finish migrating the wiki documentation to adoc files. I think its
>>>>>>>> most of the EIP patterns that are missing. There is a basic list of
>>>>>>>> EIPs here: https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc
>>>>>>>>
>>>>>>>> 2)
>>>>>>>> Generate documentation and website. Maybe documentation first and then
>>>>>>>> we come up with a modern website later - when we have a new logo as
>>>>>>>> well.
>>>>>>>>
>>>>>>>> 3)
>>>>>>>> Mark more stuff to @deprecate so we dont drag them into Camel 3.0.
>>>>>>>> This is both components / and other artifacts.
>>>>>>>> And as well the camel-core APIs where there is maybe more we can deprecate.
>>>>>>>> For example the old stuff that was created prior to the component docs
>>>>>>>> we do now with the apt plugin at build time instead of this old code
>>>>>>>> with runtime that dont really pan out anyway.
>>>>>>>>
>>>>>>>> 4)
>>>>>>>> Move spring-boot starters into the platforms folder. There is a ticket
>>>>>>>> about this.
>>>>>>>>
>>>>>>>> 5)
>>>>>>>> More improvements to spring boot auto configuration. We have a bunch
>>>>>>>> of tickets on that.
>>>>>>>>
>>>>>>>> 6)
>>>>>>>> Look at the health check API and see if there is something we can get
>>>>>>>> started on.
>>>>>>>> Possible some API to integrate with spring boot actuators (when using
>>>>>>>> SB) and allow each component to provide their own checks so they can
>>>>>>>> be implemented ad-hoc. There is a ticket about this.
>>>>>>>>
>>>>>>>> 7)
>>>>>>>> Possible some more teaks to camel-catalog based on feedback from IDEA
>>>>>>>> plugin and the maven validate goal.
>>>>>>>>
>>>>>>>> 8)
>>>>>>>> That CDI JEE transaction PR on github.
>>>>>>>> Ideally we would have had a transaction API in camel-core and then one
>>>>>>>> impl for camel-spring, and then another for camel-cdi-jee. But that
>>>>>>>> may require too much work.
>>>>>>>>
>>>>>>>> 9)
>>>>>>>> Work on the Java 8 DSL such as get more community feedback, and then
>>>>>>>> resolve the TODOs with the documentation updates and look into other
>>>>>>>> areas where the API can benefit from Java 8 lambdas and whatnot. I
>>>>>>>> dont think we have a ticket about this.
>>>>>>>>
>>>>>>>> 10)
>>>>>>>> Karaf users may want to improve/finish up the camel-test-karaf module
>>>>>>>> so its more usable and end users can use it to test integration tests
>>>>>>>> with Camel and Karaf.
>>>>>>>>
>>>>>>>> 11)
>>>>>>>> Introduce Camel Connectors (more about this later)
>>>>>>>>
>>>>>>>>
>>>>>>>> Anything else?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Claus Ibsen
>>>>>>>> -----------------
>>>>>>>> http://davsclaus.com @davsclaus
>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Claus Ibsen
>>>>>>> -----------------
>>>>>>> http://davsclaus.com @davsclaus
>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

Thanks Antonin that sounds great.

The JIRA tickets are down to 3
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved

We have recently fixed up the missing component docs and fixed broken
links from browsing on github.

We should keep an eye on the CI servers and output from the
camel-catalog report, to see if it reports more missing stuff.
It currently has a false positive on some missing docs for some of the
test components. I will try to fix this later today.

However thats not all. At all time feel free to have fun and work on
anything you like on Camel. There is still time for small improvements
etc. But bigger stuff we should really defer to the next release.


On Wed, Apr 12, 2017 at 3:35 PM, Antonin Stefanutti
<an...@stefanutti.fr> wrote:
>
>> On 12 Apr 2017, at 15:22, Claus Ibsen <cl...@gmail.com> wrote:
>>
>> Hi
>>
>> Just a heads up that we plan to cut the RC for Camel 2.19 next week.
>>
>> So we are closing down on the last tickets, bugs, features etc to get
>> the code base in shape.
>>
>> The JIRA has 9 tickets
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved
>>
>> But you are of course welcome to work on other tickets etc but just
>> mind any big functionality is likely better to wait for next release.
>>
>> There is however the expected transaction stuff for CDI as a PR in the
>> works, and also a new iot component
>> https://github.com/apache/camel/pulls
>
> The CDI transaction support PR should be merged by end of week.
>
> https://github.com/apache/camel/pull/1390
>
>> We should keep an eye on the CI servers to see how they are and fix
>> any test failures etc. Recently we got them to build and test the OSGi
>> and spring-boot specific tests so we should be able to better keep an
>> eye on this now and in the future.
>> https://builds.apache.org/view/A-D/view/Camel/
>>
>>
>>
>>
>>
>> On Fri, Apr 7, 2017 at 8:45 AM, Gregor Zurowski
>> <gr...@list.zurowski.org> wrote:
>>> Hi Claus,
>>>
>>> Week 16 works for me.  I will send out another email shortly before
>>> starting to build the RC.
>>>
>>> Thanks,
>>> Gregor
>>>
>>>
>>> On Wed, Apr 5, 2017 at 3:08 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>> Hi Gregor
>>>>
>>>> Yeah its April so we should get the 2.19.0 release out the door.
>>>>
>>>> We have just setup a 2.20.0 version in JIRA and folks should start
>>>> moving their tickets to that version if its something that they cannot
>>>> finish in time. Also we should refrain from doing bigger work at this
>>>> time as we should close down on last tickets, bug fixes, and get the
>>>> CI tests in good order, etc.
>>>>
>>>> I will look at the JIRAs later this week and cleanup a bit so we have
>>>> a better overview of what work is yet to be done.
>>>>
>>>> As April has the easter holidays. I wonder what you time schedule looks like?
>>>>
>>>> Maybe if you have time to help with the release after the holidays?
>>>>
>>>> Week 16 and 17 are the last 2 weeks in April after the holidays.
>>>> If we could maybe cut the RC in week 16 then that would be good.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, Apr 3, 2017 at 2:14 PM, Gregor Zurowski
>>>> <gr...@list.zurowski.org> wrote:
>>>>> Hi,
>>>>>
>>>>> Are we getting closer to build a 2.19.0 release?  I would volunteer
>>>>> for creating the release, just wanted to check when would be a good
>>>>> time to do so.
>>>>>
>>>>> Thanks,
>>>>> Gregor
>>>>>
>>>>>
>>>>> On Wed, Mar 15, 2017 at 9:29 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>> Hi
>>>>>>
>>>>>> Just wanted to bring up that we are closing in on a good time for
>>>>>> doing a new release.
>>>>>>
>>>>>> For example in mid April it would be around 6 months since the last
>>>>>> 2.18.0 release.
>>>>>>
>>>>>> Therefore we should start closing down and fixing bugs, and make sure
>>>>>> the CI servers and tests are in good shape.
>>>>>> This morning we have fixed a number of recent test failures and are
>>>>>> down to only 1 test failure now.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Jan 16, 2017 at 10:28 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>> Hi
>>>>>>>
>>>>>>> There is a bunch of stuff which we can/should have on the roadmap to
>>>>>>> complete for the Camel 2.19 release.
>>>>>>>
>>>>>>> Here is on top of my head
>>>>>>>
>>>>>>> 1)
>>>>>>> Finish migrating the wiki documentation to adoc files. I think its
>>>>>>> most of the EIP patterns that are missing. There is a basic list of
>>>>>>> EIPs here: https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc
>>>>>>>
>>>>>>> 2)
>>>>>>> Generate documentation and website. Maybe documentation first and then
>>>>>>> we come up with a modern website later - when we have a new logo as
>>>>>>> well.
>>>>>>>
>>>>>>> 3)
>>>>>>> Mark more stuff to @deprecate so we dont drag them into Camel 3.0.
>>>>>>> This is both components / and other artifacts.
>>>>>>> And as well the camel-core APIs where there is maybe more we can deprecate.
>>>>>>> For example the old stuff that was created prior to the component docs
>>>>>>> we do now with the apt plugin at build time instead of this old code
>>>>>>> with runtime that dont really pan out anyway.
>>>>>>>
>>>>>>> 4)
>>>>>>> Move spring-boot starters into the platforms folder. There is a ticket
>>>>>>> about this.
>>>>>>>
>>>>>>> 5)
>>>>>>> More improvements to spring boot auto configuration. We have a bunch
>>>>>>> of tickets on that.
>>>>>>>
>>>>>>> 6)
>>>>>>> Look at the health check API and see if there is something we can get
>>>>>>> started on.
>>>>>>> Possible some API to integrate with spring boot actuators (when using
>>>>>>> SB) and allow each component to provide their own checks so they can
>>>>>>> be implemented ad-hoc. There is a ticket about this.
>>>>>>>
>>>>>>> 7)
>>>>>>> Possible some more teaks to camel-catalog based on feedback from IDEA
>>>>>>> plugin and the maven validate goal.
>>>>>>>
>>>>>>> 8)
>>>>>>> That CDI JEE transaction PR on github.
>>>>>>> Ideally we would have had a transaction API in camel-core and then one
>>>>>>> impl for camel-spring, and then another for camel-cdi-jee. But that
>>>>>>> may require too much work.
>>>>>>>
>>>>>>> 9)
>>>>>>> Work on the Java 8 DSL such as get more community feedback, and then
>>>>>>> resolve the TODOs with the documentation updates and look into other
>>>>>>> areas where the API can benefit from Java 8 lambdas and whatnot. I
>>>>>>> dont think we have a ticket about this.
>>>>>>>
>>>>>>> 10)
>>>>>>> Karaf users may want to improve/finish up the camel-test-karaf module
>>>>>>> so its more usable and end users can use it to test integration tests
>>>>>>> with Camel and Karaf.
>>>>>>>
>>>>>>> 11)
>>>>>>> Introduce Camel Connectors (more about this later)
>>>>>>>
>>>>>>>
>>>>>>> Anything else?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Claus Ibsen
>>>>>>> -----------------
>>>>>>> http://davsclaus.com @davsclaus
>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> http://davsclaus.com @davsclaus
>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Antonin Stefanutti <an...@stefanutti.fr>.
> On 12 Apr 2017, at 15:22, Claus Ibsen <cl...@gmail.com> wrote:
> 
> Hi
> 
> Just a heads up that we plan to cut the RC for Camel 2.19 next week.
> 
> So we are closing down on the last tickets, bugs, features etc to get
> the code base in shape.
> 
> The JIRA has 9 tickets
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved
> 
> But you are of course welcome to work on other tickets etc but just
> mind any big functionality is likely better to wait for next release.
> 
> There is however the expected transaction stuff for CDI as a PR in the
> works, and also a new iot component
> https://github.com/apache/camel/pulls

The CDI transaction support PR should be merged by end of week.

https://github.com/apache/camel/pull/1390

> We should keep an eye on the CI servers to see how they are and fix
> any test failures etc. Recently we got them to build and test the OSGi
> and spring-boot specific tests so we should be able to better keep an
> eye on this now and in the future.
> https://builds.apache.org/view/A-D/view/Camel/
> 
> 
> 
> 
> 
> On Fri, Apr 7, 2017 at 8:45 AM, Gregor Zurowski
> <gr...@list.zurowski.org> wrote:
>> Hi Claus,
>> 
>> Week 16 works for me.  I will send out another email shortly before
>> starting to build the RC.
>> 
>> Thanks,
>> Gregor
>> 
>> 
>> On Wed, Apr 5, 2017 at 3:08 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>> Hi Gregor
>>> 
>>> Yeah its April so we should get the 2.19.0 release out the door.
>>> 
>>> We have just setup a 2.20.0 version in JIRA and folks should start
>>> moving their tickets to that version if its something that they cannot
>>> finish in time. Also we should refrain from doing bigger work at this
>>> time as we should close down on last tickets, bug fixes, and get the
>>> CI tests in good order, etc.
>>> 
>>> I will look at the JIRAs later this week and cleanup a bit so we have
>>> a better overview of what work is yet to be done.
>>> 
>>> As April has the easter holidays. I wonder what you time schedule looks like?
>>> 
>>> Maybe if you have time to help with the release after the holidays?
>>> 
>>> Week 16 and 17 are the last 2 weeks in April after the holidays.
>>> If we could maybe cut the RC in week 16 then that would be good.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Mon, Apr 3, 2017 at 2:14 PM, Gregor Zurowski
>>> <gr...@list.zurowski.org> wrote:
>>>> Hi,
>>>> 
>>>> Are we getting closer to build a 2.19.0 release?  I would volunteer
>>>> for creating the release, just wanted to check when would be a good
>>>> time to do so.
>>>> 
>>>> Thanks,
>>>> Gregor
>>>> 
>>>> 
>>>> On Wed, Mar 15, 2017 at 9:29 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>> Hi
>>>>> 
>>>>> Just wanted to bring up that we are closing in on a good time for
>>>>> doing a new release.
>>>>> 
>>>>> For example in mid April it would be around 6 months since the last
>>>>> 2.18.0 release.
>>>>> 
>>>>> Therefore we should start closing down and fixing bugs, and make sure
>>>>> the CI servers and tests are in good shape.
>>>>> This morning we have fixed a number of recent test failures and are
>>>>> down to only 1 test failure now.
>>>>> 
>>>>> 
>>>>> 
>>>>> On Mon, Jan 16, 2017 at 10:28 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>> Hi
>>>>>> 
>>>>>> There is a bunch of stuff which we can/should have on the roadmap to
>>>>>> complete for the Camel 2.19 release.
>>>>>> 
>>>>>> Here is on top of my head
>>>>>> 
>>>>>> 1)
>>>>>> Finish migrating the wiki documentation to adoc files. I think its
>>>>>> most of the EIP patterns that are missing. There is a basic list of
>>>>>> EIPs here: https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc
>>>>>> 
>>>>>> 2)
>>>>>> Generate documentation and website. Maybe documentation first and then
>>>>>> we come up with a modern website later - when we have a new logo as
>>>>>> well.
>>>>>> 
>>>>>> 3)
>>>>>> Mark more stuff to @deprecate so we dont drag them into Camel 3.0.
>>>>>> This is both components / and other artifacts.
>>>>>> And as well the camel-core APIs where there is maybe more we can deprecate.
>>>>>> For example the old stuff that was created prior to the component docs
>>>>>> we do now with the apt plugin at build time instead of this old code
>>>>>> with runtime that dont really pan out anyway.
>>>>>> 
>>>>>> 4)
>>>>>> Move spring-boot starters into the platforms folder. There is a ticket
>>>>>> about this.
>>>>>> 
>>>>>> 5)
>>>>>> More improvements to spring boot auto configuration. We have a bunch
>>>>>> of tickets on that.
>>>>>> 
>>>>>> 6)
>>>>>> Look at the health check API and see if there is something we can get
>>>>>> started on.
>>>>>> Possible some API to integrate with spring boot actuators (when using
>>>>>> SB) and allow each component to provide their own checks so they can
>>>>>> be implemented ad-hoc. There is a ticket about this.
>>>>>> 
>>>>>> 7)
>>>>>> Possible some more teaks to camel-catalog based on feedback from IDEA
>>>>>> plugin and the maven validate goal.
>>>>>> 
>>>>>> 8)
>>>>>> That CDI JEE transaction PR on github.
>>>>>> Ideally we would have had a transaction API in camel-core and then one
>>>>>> impl for camel-spring, and then another for camel-cdi-jee. But that
>>>>>> may require too much work.
>>>>>> 
>>>>>> 9)
>>>>>> Work on the Java 8 DSL such as get more community feedback, and then
>>>>>> resolve the TODOs with the documentation updates and look into other
>>>>>> areas where the API can benefit from Java 8 lambdas and whatnot. I
>>>>>> dont think we have a ticket about this.
>>>>>> 
>>>>>> 10)
>>>>>> Karaf users may want to improve/finish up the camel-test-karaf module
>>>>>> so its more usable and end users can use it to test integration tests
>>>>>> with Camel and Karaf.
>>>>>> 
>>>>>> 11)
>>>>>> Introduce Camel Connectors (more about this later)
>>>>>> 
>>>>>> 
>>>>>> Anything else?
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> http://davsclaus.com @davsclaus
>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>> 
>>> 
>>> 
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
> 
> 
> 
> -- 
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

Just a heads up that we plan to cut the RC for Camel 2.19 next week.

So we are closing down on the last tickets, bugs, features etc to get
the code base in shape.

The JIRA has 9 tickets
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved

But you are of course welcome to work on other tickets etc but just
mind any big functionality is likely better to wait for next release.

There is however the expected transaction stuff for CDI as a PR in the
works, and also a new iot component
https://github.com/apache/camel/pulls

We should keep an eye on the CI servers to see how they are and fix
any test failures etc. Recently we got them to build and test the OSGi
and spring-boot specific tests so we should be able to better keep an
eye on this now and in the future.
https://builds.apache.org/view/A-D/view/Camel/





On Fri, Apr 7, 2017 at 8:45 AM, Gregor Zurowski
<gr...@list.zurowski.org> wrote:
> Hi Claus,
>
> Week 16 works for me.  I will send out another email shortly before
> starting to build the RC.
>
> Thanks,
> Gregor
>
>
> On Wed, Apr 5, 2017 at 3:08 PM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi Gregor
>>
>> Yeah its April so we should get the 2.19.0 release out the door.
>>
>> We have just setup a 2.20.0 version in JIRA and folks should start
>> moving their tickets to that version if its something that they cannot
>> finish in time. Also we should refrain from doing bigger work at this
>> time as we should close down on last tickets, bug fixes, and get the
>> CI tests in good order, etc.
>>
>> I will look at the JIRAs later this week and cleanup a bit so we have
>> a better overview of what work is yet to be done.
>>
>> As April has the easter holidays. I wonder what you time schedule looks like?
>>
>> Maybe if you have time to help with the release after the holidays?
>>
>> Week 16 and 17 are the last 2 weeks in April after the holidays.
>> If we could maybe cut the RC in week 16 then that would be good.
>>
>>
>>
>>
>>
>> On Mon, Apr 3, 2017 at 2:14 PM, Gregor Zurowski
>> <gr...@list.zurowski.org> wrote:
>>> Hi,
>>>
>>> Are we getting closer to build a 2.19.0 release?  I would volunteer
>>> for creating the release, just wanted to check when would be a good
>>> time to do so.
>>>
>>> Thanks,
>>> Gregor
>>>
>>>
>>> On Wed, Mar 15, 2017 at 9:29 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>> Hi
>>>>
>>>> Just wanted to bring up that we are closing in on a good time for
>>>> doing a new release.
>>>>
>>>> For example in mid April it would be around 6 months since the last
>>>> 2.18.0 release.
>>>>
>>>> Therefore we should start closing down and fixing bugs, and make sure
>>>> the CI servers and tests are in good shape.
>>>> This morning we have fixed a number of recent test failures and are
>>>> down to only 1 test failure now.
>>>>
>>>>
>>>>
>>>> On Mon, Jan 16, 2017 at 10:28 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>> Hi
>>>>>
>>>>> There is a bunch of stuff which we can/should have on the roadmap to
>>>>> complete for the Camel 2.19 release.
>>>>>
>>>>> Here is on top of my head
>>>>>
>>>>> 1)
>>>>> Finish migrating the wiki documentation to adoc files. I think its
>>>>> most of the EIP patterns that are missing. There is a basic list of
>>>>> EIPs here: https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc
>>>>>
>>>>> 2)
>>>>> Generate documentation and website. Maybe documentation first and then
>>>>> we come up with a modern website later - when we have a new logo as
>>>>> well.
>>>>>
>>>>> 3)
>>>>> Mark more stuff to @deprecate so we dont drag them into Camel 3.0.
>>>>> This is both components / and other artifacts.
>>>>> And as well the camel-core APIs where there is maybe more we can deprecate.
>>>>> For example the old stuff that was created prior to the component docs
>>>>> we do now with the apt plugin at build time instead of this old code
>>>>> with runtime that dont really pan out anyway.
>>>>>
>>>>> 4)
>>>>> Move spring-boot starters into the platforms folder. There is a ticket
>>>>> about this.
>>>>>
>>>>> 5)
>>>>> More improvements to spring boot auto configuration. We have a bunch
>>>>> of tickets on that.
>>>>>
>>>>> 6)
>>>>> Look at the health check API and see if there is something we can get
>>>>> started on.
>>>>> Possible some API to integrate with spring boot actuators (when using
>>>>> SB) and allow each component to provide their own checks so they can
>>>>> be implemented ad-hoc. There is a ticket about this.
>>>>>
>>>>> 7)
>>>>> Possible some more teaks to camel-catalog based on feedback from IDEA
>>>>> plugin and the maven validate goal.
>>>>>
>>>>> 8)
>>>>> That CDI JEE transaction PR on github.
>>>>> Ideally we would have had a transaction API in camel-core and then one
>>>>> impl for camel-spring, and then another for camel-cdi-jee. But that
>>>>> may require too much work.
>>>>>
>>>>> 9)
>>>>> Work on the Java 8 DSL such as get more community feedback, and then
>>>>> resolve the TODOs with the documentation updates and look into other
>>>>> areas where the API can benefit from Java 8 lambdas and whatnot. I
>>>>> dont think we have a ticket about this.
>>>>>
>>>>> 10)
>>>>> Karaf users may want to improve/finish up the camel-test-karaf module
>>>>> so its more usable and end users can use it to test integration tests
>>>>> with Camel and Karaf.
>>>>>
>>>>> 11)
>>>>> Introduce Camel Connectors (more about this later)
>>>>>
>>>>>
>>>>> Anything else?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Gregor Zurowski <gr...@list.zurowski.org>.
Hi Claus,

Week 16 works for me.  I will send out another email shortly before
starting to build the RC.

Thanks,
Gregor


On Wed, Apr 5, 2017 at 3:08 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi Gregor
>
> Yeah its April so we should get the 2.19.0 release out the door.
>
> We have just setup a 2.20.0 version in JIRA and folks should start
> moving their tickets to that version if its something that they cannot
> finish in time. Also we should refrain from doing bigger work at this
> time as we should close down on last tickets, bug fixes, and get the
> CI tests in good order, etc.
>
> I will look at the JIRAs later this week and cleanup a bit so we have
> a better overview of what work is yet to be done.
>
> As April has the easter holidays. I wonder what you time schedule looks like?
>
> Maybe if you have time to help with the release after the holidays?
>
> Week 16 and 17 are the last 2 weeks in April after the holidays.
> If we could maybe cut the RC in week 16 then that would be good.
>
>
>
>
>
> On Mon, Apr 3, 2017 at 2:14 PM, Gregor Zurowski
> <gr...@list.zurowski.org> wrote:
>> Hi,
>>
>> Are we getting closer to build a 2.19.0 release?  I would volunteer
>> for creating the release, just wanted to check when would be a good
>> time to do so.
>>
>> Thanks,
>> Gregor
>>
>>
>> On Wed, Mar 15, 2017 at 9:29 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>> Hi
>>>
>>> Just wanted to bring up that we are closing in on a good time for
>>> doing a new release.
>>>
>>> For example in mid April it would be around 6 months since the last
>>> 2.18.0 release.
>>>
>>> Therefore we should start closing down and fixing bugs, and make sure
>>> the CI servers and tests are in good shape.
>>> This morning we have fixed a number of recent test failures and are
>>> down to only 1 test failure now.
>>>
>>>
>>>
>>> On Mon, Jan 16, 2017 at 10:28 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>> Hi
>>>>
>>>> There is a bunch of stuff which we can/should have on the roadmap to
>>>> complete for the Camel 2.19 release.
>>>>
>>>> Here is on top of my head
>>>>
>>>> 1)
>>>> Finish migrating the wiki documentation to adoc files. I think its
>>>> most of the EIP patterns that are missing. There is a basic list of
>>>> EIPs here: https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc
>>>>
>>>> 2)
>>>> Generate documentation and website. Maybe documentation first and then
>>>> we come up with a modern website later - when we have a new logo as
>>>> well.
>>>>
>>>> 3)
>>>> Mark more stuff to @deprecate so we dont drag them into Camel 3.0.
>>>> This is both components / and other artifacts.
>>>> And as well the camel-core APIs where there is maybe more we can deprecate.
>>>> For example the old stuff that was created prior to the component docs
>>>> we do now with the apt plugin at build time instead of this old code
>>>> with runtime that dont really pan out anyway.
>>>>
>>>> 4)
>>>> Move spring-boot starters into the platforms folder. There is a ticket
>>>> about this.
>>>>
>>>> 5)
>>>> More improvements to spring boot auto configuration. We have a bunch
>>>> of tickets on that.
>>>>
>>>> 6)
>>>> Look at the health check API and see if there is something we can get
>>>> started on.
>>>> Possible some API to integrate with spring boot actuators (when using
>>>> SB) and allow each component to provide their own checks so they can
>>>> be implemented ad-hoc. There is a ticket about this.
>>>>
>>>> 7)
>>>> Possible some more teaks to camel-catalog based on feedback from IDEA
>>>> plugin and the maven validate goal.
>>>>
>>>> 8)
>>>> That CDI JEE transaction PR on github.
>>>> Ideally we would have had a transaction API in camel-core and then one
>>>> impl for camel-spring, and then another for camel-cdi-jee. But that
>>>> may require too much work.
>>>>
>>>> 9)
>>>> Work on the Java 8 DSL such as get more community feedback, and then
>>>> resolve the TODOs with the documentation updates and look into other
>>>> areas where the API can benefit from Java 8 lambdas and whatnot. I
>>>> dont think we have a ticket about this.
>>>>
>>>> 10)
>>>> Karaf users may want to improve/finish up the camel-test-karaf module
>>>> so its more usable and end users can use it to test integration tests
>>>> with Camel and Karaf.
>>>>
>>>> 11)
>>>> Introduce Camel Connectors (more about this later)
>>>>
>>>>
>>>> Anything else?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

Posted by Claus Ibsen <cl...@gmail.com>.
Hi Gregor

Yeah its April so we should get the 2.19.0 release out the door.

We have just setup a 2.20.0 version in JIRA and folks should start
moving their tickets to that version if its something that they cannot
finish in time. Also we should refrain from doing bigger work at this
time as we should close down on last tickets, bug fixes, and get the
CI tests in good order, etc.

I will look at the JIRAs later this week and cleanup a bit so we have
a better overview of what work is yet to be done.

As April has the easter holidays. I wonder what you time schedule looks like?

Maybe if you have time to help with the release after the holidays?

Week 16 and 17 are the last 2 weeks in April after the holidays.
If we could maybe cut the RC in week 16 then that would be good.





On Mon, Apr 3, 2017 at 2:14 PM, Gregor Zurowski
<gr...@list.zurowski.org> wrote:
> Hi,
>
> Are we getting closer to build a 2.19.0 release?  I would volunteer
> for creating the release, just wanted to check when would be a good
> time to do so.
>
> Thanks,
> Gregor
>
>
> On Wed, Mar 15, 2017 at 9:29 AM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi
>>
>> Just wanted to bring up that we are closing in on a good time for
>> doing a new release.
>>
>> For example in mid April it would be around 6 months since the last
>> 2.18.0 release.
>>
>> Therefore we should start closing down and fixing bugs, and make sure
>> the CI servers and tests are in good shape.
>> This morning we have fixed a number of recent test failures and are
>> down to only 1 test failure now.
>>
>>
>>
>> On Mon, Jan 16, 2017 at 10:28 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>> Hi
>>>
>>> There is a bunch of stuff which we can/should have on the roadmap to
>>> complete for the Camel 2.19 release.
>>>
>>> Here is on top of my head
>>>
>>> 1)
>>> Finish migrating the wiki documentation to adoc files. I think its
>>> most of the EIP patterns that are missing. There is a basic list of
>>> EIPs here: https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc
>>>
>>> 2)
>>> Generate documentation and website. Maybe documentation first and then
>>> we come up with a modern website later - when we have a new logo as
>>> well.
>>>
>>> 3)
>>> Mark more stuff to @deprecate so we dont drag them into Camel 3.0.
>>> This is both components / and other artifacts.
>>> And as well the camel-core APIs where there is maybe more we can deprecate.
>>> For example the old stuff that was created prior to the component docs
>>> we do now with the apt plugin at build time instead of this old code
>>> with runtime that dont really pan out anyway.
>>>
>>> 4)
>>> Move spring-boot starters into the platforms folder. There is a ticket
>>> about this.
>>>
>>> 5)
>>> More improvements to spring boot auto configuration. We have a bunch
>>> of tickets on that.
>>>
>>> 6)
>>> Look at the health check API and see if there is something we can get
>>> started on.
>>> Possible some API to integrate with spring boot actuators (when using
>>> SB) and allow each component to provide their own checks so they can
>>> be implemented ad-hoc. There is a ticket about this.
>>>
>>> 7)
>>> Possible some more teaks to camel-catalog based on feedback from IDEA
>>> plugin and the maven validate goal.
>>>
>>> 8)
>>> That CDI JEE transaction PR on github.
>>> Ideally we would have had a transaction API in camel-core and then one
>>> impl for camel-spring, and then another for camel-cdi-jee. But that
>>> may require too much work.
>>>
>>> 9)
>>> Work on the Java 8 DSL such as get more community feedback, and then
>>> resolve the TODOs with the documentation updates and look into other
>>> areas where the API can benefit from Java 8 lambdas and whatnot. I
>>> dont think we have a ticket about this.
>>>
>>> 10)
>>> Karaf users may want to improve/finish up the camel-test-karaf module
>>> so its more usable and end users can use it to test integration tests
>>> with Camel and Karaf.
>>>
>>> 11)
>>> Introduce Camel Connectors (more about this later)
>>>
>>>
>>> Anything else?
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2