[GitHub] camel pull request #2248: CAMEL-11497 - add missing to-eip.adoc toD-eip.adoc...

[onderson]

Github user onderson closed the pull request at:

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


---

[GitHub] camel pull request #2248: CAMEL-11497 - add missing to-eip.adoc toD-eip.adoc...

[onderson]

GitHub user onderson opened a pull request:

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

CAMEL-11497 - add missing to-eip.adoc toD-eip.adoc transform-eip.adoc…

… process-eip.adoc

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/onderson/camel CAMEL-11497

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/2248.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2248


commit ca25f415cf27e471283c296754e12414fc5daf2d
Author: Sezgin 
Date:   2018-03-08T07:23:35Z

CAMEL-11497 - add missing to-eip.adoc toD-eip.adoc transform-eip.adoc 
process-eip.adoc




---

[GitHub] camel pull request #2247: add https to resource helper

[yulgit1]

GitHub user yulgit1 opened a pull request:

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

add https to resource helper

allows using 'document' function with https endpoint

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yulgit1/camel resourcehelper-https

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/2247.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2247


commit 9a062d251871ea98b3fc40517b95e128338fe8fe
Author: Eric James 
Date:   2018-03-08T07:14:33Z

add https to resource helper




---

Re: Getting ready for Apache Camel 2.21 release

[Claus Ibsen]

Hi

So the CI builds had 3 successfully builds recently
https://builds.apache.org/job/Camel/job/master/

The build #120 was hanging and I killed it, and it started a new build #121.
That build should have a fix that caused the previous builds to fail
with due to a recent cdi-pax upgrade.

We have today and tomorrow morning to get the bits in, before we hand
it over to Gregor, to cut the release.


On Tue, Mar 6, 2018 at 11:04 AM, Andrea Cosentino  wrote:
> Hello,
>
> Actually we have the SMX bundles release of February under vote. The bundles 
> are here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311206=12342774
>
> I believe Saxon, gRPC and OkHttp 3.10 should be included in 2.21.0 (and 
> others maybe, but with less importance), the vote should close soon, I should 
> be able to update everything before Friday.
>
>
>
>
> --
> Andrea Cosentino
> --
> Apache Camel PMC Member
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Tuesday, March 6, 2018, 10:58:23 AM GMT+1, Claus Ibsen 
>  wrote:
>
>
>
>
>
> Hi
>
> So this week we are closing in on getting ready for cutting the Camel
> 2.21.0 release in the weekend.
>
> The CI server are doing many tests and we have improved and fixed some
> of its failures, and also found some flaky tests that we have
> disabled.
> https://builds.apache.org/job/Camel/job/master/
>
> There are 10 JIRAs assigned for 2.21.0 and I will go over them
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.21.0%20AND%20statusCategory%20%3D%20new
>
> Some of these will be moved to 2.22.0 or 2.21.1.
>
> Otherwise we should focus on bug fixes, smaller improvements, polish
> the docs, examples etc.
>
>
> Andrea is there any SMX bundle release we potentially are waiting for?
>
>
>
> On Sun, Mar 4, 2018 at 9:22 AM, Claus Ibsen  wrote:
>> Hi
>>
>> On Sun, Mar 4, 2018 at 9:19 AM, Alex Dettinger  wrote:
>>> Hi,
>>>
>>>  Just a quick note that I had a successful build this night on my local
>>> machine too.
>>>
>>
>> Thanks for testing and reporting back.
>>
>>
>>> Alex
>>>
>>> On Wed, Feb 28, 2018 at 10:34 AM, Claus Ibsen  wrote:
>>>
 Hi

 We have now moved some JIRA tickets to 2.22 so the roadmap for 2.21 is
 shorter and also what we would actually focus on.
 That said if there is something you really would like to get in 2.21
 that was moved to 2.22 then say so, and work on it.
 We have this week to work on improvements, new features etc. And then
 next week we should focus mostly on bug fixes, polishing, testing, and
 fix up docs etc.
 And then Gregor will cut the release in the weekend (eg around March
 9-11th)

 I ran tests overnight and found 3 issues which I have logged and fixed
 this morning.
 So all tests pass on my laptop, but would also be good to have tested
 on other platforms.

 The CI servers are temporary disabled and we are migrating to Jenkins
 Pipeline to make the CI server jobs more faster and less resource
 intensive.
 There is another talk on @dev about this.




 On Mon, Feb 26, 2018 at 10:10 AM, Claus Ibsen 
 wrote:
 > Hi
 >
 > We should start to close down and get ready for the expected Camel 2.21
 release.
 >
 > If you have any new functionality then its last call to get that
 > implemented and committed.
 >
 > There are currently 61 tickets [1] assigned to 2.21.0 release which is
 > too much. I will go over them and you are of course also welcome to
 > take a look, and move tickets to 2.21.1 or 2.22.0.
 >
 > I think we need to use this week to get the last tickets resolved,
 > bugs fixed, stable the CI tests and what else, and then we can touch
 > base in start of next week to plan for cutting the 2.21 RC builds.
 > Gregor do you have time for example from next week / next weekend to
 > cut the RC?
 >
 >
 > [1] - https://issues.apache.org/jira/issues/?jql=project%20%
 3D%20CAMEL%20AND%20fixVersion%20%3D%202.21.0%20AND%
 20statusCategory%20%3D%20new
 >
 >
 >
 >
 >
 > --
 > 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

[GitHub] camel pull request #2246: https support in ResourceHelper

[oscerd]

Github user oscerd closed the pull request at:

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


---

[GitHub] camel pull request #2246: https support in ResourceHelper

[yulgit1]

GitHub user yulgit1 opened a pull request:

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

https support in ResourceHelper

allows using 'document' function with https endpoint 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yulgit1/camel 2.20.2-erj-https

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/2246.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2246


commit 6ac4066b36e626020885d7549e04f45583f68871
Author: Claus Ibsen 
Date:   2017-10-09T18:19:03Z

CAMEL-11890: camel-connector - Use JSon parser to parse the 
camel-connector-schema.json.

commit 82d77149a1de459add8e45a3e6854ed84eeb5e8d
Author: Claus Ibsen 
Date:   2017-10-11T13:25:41Z

CAMEL-11895: camel-hystrix - Expose state of circuit breaker on JMX mbean / 
java api on processor.

commit 854f462c03ff77b5eef1e68055ab0f3b8993ecf0
Author: Frédérik Rouleau 
Date:   2017-10-11T08:39:53Z

CAMEL-11894: camel-karaf-commands deployment failed on karaf 4.0

commit 72fe78719af099aebc51b009f849a37e5896155f
Author: Claus Ibsen 
Date:   2017-10-12T09:50:30Z

Upgrade spring

commit 54b34c9708c6ffac5c4eb45e42372881ddd48b94
Author: lburgazzoli 
Date:   2017-10-12T12:59:01Z

CAMEL-11900: cluster-service : only the first event listener is notified 
about cluster events

commit fbb97efb26f46fb734c7c48c36b67119016ae520
Author: richardgroote <32516488+richardgroote@...>
Date:   2017-10-12T09:33:35Z

CAMEL-11898: Attachment are not in the response

commit 27fd53285bc503114b2e4cff14d9d6a640857e10
Author: Claus Ibsen 
Date:   2017-10-12T13:58:32Z

CAMEL-11898: Polished. This closes #2030

commit 0be79c6ed1aff216d0bbbe1d4db02b57540187cd
Author: aldettinger 
Date:   2017-10-12T13:18:02Z

CAMEL: Fixed a javadoc warning in camel-bindy

commit cf32b912e153f389258f8293d0e0761ec131ad00
Author: onders86 
Date:   2017-10-12T07:19:33Z

CAMEL-11892 - breadcrumbId class cast failure if other than SAAJ used as 
WebServiceMessage impl

commit b7ea171209efdfef8a132c596772460a57bf365d
Author: lburgazzoli 
Date:   2017-10-12T16:52:50Z

CAMEL-11902: cluster-service : FileLockClusterView should not always return 
local member as leader

commit c412e5d1e32491a74fe18c6ba8460b7cc53d0cfd
Author: Melissa Flinn 
Date:   2017-10-12T17:40:46Z

fuse-doc-2017 updated links to box.com

commit 370aa61f6e821a0f38a96594e5f98d2cf40f46ca
Author: Thomas Diesler 
Date:   2017-10-09T15:22:56Z

[CAMEL-11889] Kie assumes that the TCCL can load its services

commit b8eabcd0510bca1256e9678c1e9fca92977122bb
Author: Andrea Cosentino 
Date:   2017-10-11T12:34:03Z

Upgrade Java-util to version 1.31.1

commit 768a70c43fddb443a6d3f456f7dee6c98488aedb
Author: Andrea Cosentino 
Date:   2017-10-13T13:27:52Z

Regen

commit 6dd9d211dad5b607af4323f5c7e2fabda5463143
Author: Kui LIU 
Date:   2017-10-13T16:06:47Z

Replace the Number.valueOf method with the Number.parseXXX method.

It is more efficient to use the static parseXXX method to extract unboxed 
primitive value from a String.

http://findbugs.sourceforge.net/bugDescriptions.html#DM_BOXED_PRIMITIVE_FOR_PARSING

commit f6d794f7d07b2b95502639fd478eb025c9a85c81
Author: Claus Ibsen 
Date:   2017-10-14T12:24:08Z

CAMEL-11909: camel-catalog-maven - Cannot load out of the box components

commit 0fe49998eac127969e8d9111aec9a02912d5a3b9
Author: Claus Ibsen 
Date:   2017-10-14T12:44:55Z

CAMEL-11910: camel-maven-plugin - validate should not include route ids as 
consumer urls

commit 9d24dde87abc4ee4c22c35c481a423f10943be6d
Author: Sam Ma 
Date:   2017-10-15T23:34:07Z

CAMEL-11896: set CamelLogDebugBodyMaxChars when 0 or negative

commit 43f2d5f02181c02dc015ada59909c46c9cd6036c
Author: Claus Ibsen 
Date:   2017-10-16T07:21:15Z

CAMEL-11896: Need to use -1 as unlimted as spring boot will use 0 as 
default and we dont want to set the global option if so. This closes #2040

commit 250c2899ca980ab4b4eb72de4428ecb34071c93c
Author: Zoran Regvart 
Date:   2017-10-16T13:18:10Z

CAMEL-11873: Exclude validation-api from Salesf...

...orce component

Removes `hibernate-validator` no longer needed by the Salesforce
component.

(cherry picked from commit 4e3e06e997c71562251ddb1592607cbad73e580b)

commit f28dc0a18d87fe7e45c826ebefdd63af3b2b86e7
Author: lburgazzoli 
Date:   2017-10-17T09:13:15Z

CAMEL-11916: camel-jgroups-starter : JGroupsLockClusterServiceConfiguration 
lacks getter/setters

commit 

Re: News on front page about new website and documentation

[Onder SEZGIN]

I am in. Not sure about timeline, though.

On Tue, 6 Mar 2018 at 12:49, Claus Ibsen  wrote:

> Hi
>
> I think we should post a news on the Camel front page about the
> situation with the current old website and docs vs the new website and
> docs from the source.
>
> A rough plan for the new website and docs could be
>
> - finish migrating the EIP docs
> - create new TOC for new documentation
> - copy over the good parts of the old docs for the new TOC and
> otherwise write new parts from scratch (will be ongoing through 2018)
> - build a new modern front page
> - use the new Camel logo
> - publish this to a new staging url so anyone can follow the work
>
> A work plan could be that after the 2.21 release we will finish the
> EIP migrations and get started on the TOC and gradually build up the
> new documentation. At the same time folks work on the new website with
> a new build system for publishing that, and get the tech stuff in
> order.
>
> The new front page is likely where many people may have feedback/ideas
> and it can take some time to get right - if there are more proposals
> we could run a vote etc. Also we need new content for:
> - What is Apache Camel
> - How to get started etc
>
> eg content for onboarding new users and getting them to quickly
> understand what Camel is. That information is needed on both the front
> page and some beginner pages.
>
> As we are all busy with other duties at work / life / etc. then I dont
> think we can do this quickly. And therefore I anticipate that we can
> do
>
> - a new stating url with a prototype of the new website and docs ready
> for summer 2018
> - continued work on the TOC and docs until its ready to replace the old
> site
> - switch over to new website after summer 2018 when its ready (maybe
> as part of Camel 2.23 release etc).
>
> For the news on the Camel front page, then I do think we should draft
> up a text that we can present. The stuff I wrote above is a bit
> "rough" so I think we need to come up with a new text for the Camel
> front page.
>
> Anyone wanna help with that?
>
>
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>