[ANNOUNCEMENT] Apache Camel 2.17.6 Released

[Gregor Zurowski]

The Camel community announces the immediate availability of the new
Camel 2.17.6 patch release. This release contains 17 bug fixes and
improvements applied in the past weeks by the community on the Camel
2.17.x branch.

The artifacts are published and ready for you to download [1] either
from the Apache mirrors or from the Central Maven repository. For more
details please take a look at the release notes [2, 3].

Many thanks to all who made this release possible.

On behalf of the Camel PMC,
Gregor Zurowski

[1] http://camel.apache.org/download.html
[2] http://camel.apache.org/camel-2176-release.html
[3] 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12339170=12311211

[VOTE] Release Apache Camel 2.18.3 (Attempt #2)

[Gregor Zurowski]

Hi Everyone:

This is the second vote to release Apache Camel 2.18.3, a new patch
release that includes 38 fixes and improvements.  The initial vote has
been cancelled due to a major issue with Spring Boot (see [1]).  As
the Camel project seeks for best integration with Spring Boot, we
decided to recreate a new release candidate that includes a fix for
this issue.

Release notes: 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12339161=12311211

Staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1069/

Tarballs: 
https://repository.apache.org/content/repositories/orgapachecamel-1069/org/apache/camel/apache-camel/2.18.3/

Tag: 
https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ce3c3100ee019ea4aae371ea77820d202295bc84

Please test this release candidate and cast your vote.
[ ] +1 Release the binary as Apache Camel 2.18.3
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Thanks,
Gregor

[1] https://issues.apache.org/jira/browse/CAMEL-10951

Re: [HEADS UP] - Deprecate stuff on Apache Camel 2.x

[Claus Ibsen]

On Sat, Mar 4, 2017 at 9:51 PM, Onder SEZGIN  wrote:
> +1 for luca.
>
> as some commercial companies ( i know we have many in my country ) prefer
> to move to next version of java as they get more mature. so some apis and
> components may be actibely maintained  with specific version but i propose
> to keep them as dormant maybe somebody like devs in my country may
> need to play with the code.
>

-1 to dormant

The code are around in the git repos at ASF or github.
And the code stays in 2.x. Its for 3.0 that it gets removed.

camel-groovy-dsl and camel-scala may find a new home in camel-extra if
anybody at camel-extra wants to do the work to move the code and
maintain it and do releases etc.



>
> On Fri, 3 Mar 2017 at 13:35, Luca Burgazzoli  wrote:
>
>> +1
>>
>> btw, should we have a sort of "camel dormant" repository were we can
>> put stuffs that are not actively maintained ?
>>
>> ---
>> Luca Burgazzoli
>>
>>
>> On Fri, Mar 3, 2017 at 2:30 PM, Claus Ibsen  wrote:
>> > Hi
>> >
>> > I propose to deprecate camel-guice. That module has never really been
>> > in much use / attention / maintained. And over the years guice has
>> > been pain to support / guice itself was in trouble when the leaders
>> > left and google didnt do any releases and whatnot.
>> >
>> >
>> >
>> > On Wed, Mar 1, 2017 at 9:33 AM, Claus Ibsen 
>> wrote:
>> >> Hi
>> >>
>> >> As part of CAMEL-10735:
>> https://issues.apache.org/jira/browse/CAMEL-10735
>> >>
>> >> We are deprecating code on 2.x that we anticipate to be removed in
>> >> Camel 3.0 onwards.
>> >> We have marked code as deprecated over the years, but recently got
>> >> more aggressive and deprecated more in camel-core.
>> >>
>> >> We have also marked components and other artifacts as deprecated,
>> >> which you can see in the overview on the readme file in github
>> >> https://github.com/apache/camel/blob/master/components/readme.adoc
>> >>
>> >> We have also decided to deprecate the Scala and Groovy DSL which will
>> >> be moved to camel-extra as their new home. Ticket about this:
>> >> https://issues.apache.org/jira/browse/CAMEL-10909
>> >>
>> >>
>> >> For example camel-script allows to run python, php and some other
>> >> "exotic" languages. However these can be used as security attack
>> >> vectors when these libraries have issues. And because they are very
>> >> seldom used, we could maybe deprecate some of these languages and then
>> >> allow using javaScript (nashhorn from JDK) which should offer
>> >> sufficient scripting languge. And there is always groovy as well.
>> >>
>> >> We also think about deprecating components that wont support Java 9 or
>> >> are tricky to support there, for example jibx have some issues.
>> >>
>> >>
>> >> There are potential more to be deprecated, so we welcome any feedback
>> >> from the community.
>> >>
>> >>
>> >>
>> >> --
>> >> 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
>>
> --
> Sent from my iPhone



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

Re: Most of camel-itest-osgi removed

[Tadayoshi Sato]

Thanks Claus. I understand that maintaining tests can be burden, and especially 
for flaky OSGi tests.

Thanks,
Tadayoshi

> On Mar 9, 2017, at 15:38:06, Claus Ibsen  wrote:
> 
> Hi
> 
> We dont have interrest in maintaining those tests. They sit there for
> years going untouched and break from time to time.
> 
> We only want a limited few set of tests that does a coarse grained
> sanity check of osgi.
> 
> 
> 
> 
> On Thu, Mar 9, 2017 at 1:48 AM, Tadayoshi Sato  
> wrote:
>> Hi Camel Devs,
>> 
>> I just noticed that most of camel-itest-osgi were removed nearly a year
>> ago. I understand it was due to migration of old itests to the new
>> camel-test-karaf module. But I also suspect that there were indeed some
>> useful itests that had ensured a critical regression wouldn't happen.
>> 
>> Are there any thoughts on recovering those removed itests eventually?  Or
>> doesn't it just make sense?
>> 
>> Thank you,
>> 
>> Tadayoshi
> 
> 
> 
> -- 
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2

Re: [HEADS UP] - Deprecate stuff on Apache Camel 2.x

[Claus Ibsen]

Hi

Okay so some of the scripting languages and other languages that are
EOL and has not been released in many many years are being deprecated
now
https://issues.apache.org/jira/browse/CAMEL-10973

On Wed, Mar 1, 2017 at 9:33 AM, Claus Ibsen  wrote:
> Hi
>
> As part of CAMEL-10735: https://issues.apache.org/jira/browse/CAMEL-10735
>
> We are deprecating code on 2.x that we anticipate to be removed in
> Camel 3.0 onwards.
> We have marked code as deprecated over the years, but recently got
> more aggressive and deprecated more in camel-core.
>
> We have also marked components and other artifacts as deprecated,
> which you can see in the overview on the readme file in github
> https://github.com/apache/camel/blob/master/components/readme.adoc
>
> We have also decided to deprecate the Scala and Groovy DSL which will
> be moved to camel-extra as their new home. Ticket about this:
> https://issues.apache.org/jira/browse/CAMEL-10909
>
>
> For example camel-script allows to run python, php and some other
> "exotic" languages. However these can be used as security attack
> vectors when these libraries have issues. And because they are very
> seldom used, we could maybe deprecate some of these languages and then
> allow using javaScript (nashhorn from JDK) which should offer
> sufficient scripting languge. And there is always groovy as well.
>
> We also think about deprecating components that wont support Java 9 or
> are tricky to support there, for example jibx have some issues.
>
>
> There are potential more to be deprecated, so we welcome any feedback
> from the community.
>
>
>
> --
> 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: Most of camel-itest-osgi removed

[Claus Ibsen]

Hi

We dont have interrest in maintaining those tests. They sit there for
years going untouched and break from time to time.

We only want a limited few set of tests that does a coarse grained
sanity check of osgi.




On Thu, Mar 9, 2017 at 1:48 AM, Tadayoshi Sato  wrote:
> Hi Camel Devs,
>
> I just noticed that most of camel-itest-osgi were removed nearly a year
> ago. I understand it was due to migration of old itests to the new
> camel-test-karaf module. But I also suspect that there were indeed some
> useful itests that had ensured a critical regression wouldn't happen.
>
> Are there any thoughts on recovering those removed itests eventually?  Or
> doesn't it just make sense?
>
> Thank you,
>
> Tadayoshi



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

[GitHub] camel pull request #1517: CAMEL-10964: Add an itest for Jetty reverse proxy ...

[tadayosi]

GitHub user tadayosi opened a pull request:

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

CAMEL-10964: Add an itest for Jetty reverse proxy config with @BeanInject 
in RouteBuilder

Actual fix for the issue is provided by CAMEL-10513.

https://issues.apache.org/jira/browse/CAMEL-10964

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

$ git pull https://github.com/tadayosi/camel CAMEL-10964

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

https://github.com/apache/camel/pull/1517.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 #1517


commit 99124d83d19e849c066d7ba919562be5af1ef05e
Author: Tadayoshi Sato 
Date:   2017-03-09T06:07:03Z

CAMEL-10964: Add an itest for Jetty reverse proxy config with @BeanInject 
in RouteBuilder

Actual fix for the issue is provided by CAMEL-10513.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] camel pull request #1516: Fix blueprint-cm schema location to v1.1.0 for a c...

[asfgit]

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Camel.trunk.notest - Build # 3047 - Still Failing

[Apache Jenkins Server]

The Apache Jenkins build system has built Camel.trunk.notest (build #3047)

Status: Still Failing

Check console output at https://builds.apache.org/job/Camel.trunk.notest/3047/ 
to view the results.

Camel.trunk.notest.java9 - Build # 25 - Failure

[Apache Jenkins Server]

The Apache Jenkins build system has built Camel.trunk.notest.java9 (build #25)

Status: Failure

Check console output at 
https://builds.apache.org/job/Camel.trunk.notest.java9/25/ to view the results.

[GitHub] camel pull request #1516: Fix blueprint-cm schema location to v1.1.0 for a c...

[tadayosi]

GitHub user tadayosi opened a pull request:

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

Fix blueprint-cm schema location to v1.1.0 for a camel-test-blueprint test

Let me skip filing a JIRA as the fix is so tiny.

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

$ git pull https://github.com/tadayosi/camel blueprint-cm-1_1_0

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

https://github.com/apache/camel/pull/1516.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 #1516


commit 9a0a2e2346216b0b3615ea75247af67b9b580154
Author: Tadayoshi Sato 
Date:   2017-03-09T01:52:02Z

Fix blueprint-cm schema location to v1.1.0 for a camel-test-blueprint test




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Most of camel-itest-osgi removed

[Tadayoshi Sato]

Hi Camel Devs,

I just noticed that most of camel-itest-osgi were removed nearly a year
ago. I understand it was due to migration of old itests to the new
camel-test-karaf module. But I also suspect that there were indeed some
useful itests that had ensured a critical regression wouldn't happen.

Are there any thoughts on recovering those removed itests eventually?  Or
doesn't it just make sense?

Thank you,

Tadayoshi

Re: [VOTE] Release Apache Camel 2.17.6

[Gregor Zurowski]

Thanks for your participation in this vote.  This vote passes with the
following results:

+1 binding: 6 (Andrea Cosentino, Claus Ibsen, Daniel Kulp, Gregor
Zurowski, Jean-Baptiste Onofré, Luca Burgazzoli)

+1 non-binding: 1 (Krzysztof Sobkowiak)

I will promote the artifacts for Camel 2.17.6 shortly.

Gregor


On Sun, Mar 5, 2017 at 2:33 PM, Gregor Zurowski
 wrote:
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.17.6, a new patch release
> that includes 17 fixes and improvements.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12339170=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1068/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1068/org/apache/camel/apache-camel/2.17.6/
>
> Tag: 
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=168e6c362dfeb6166a0b33c28c54027514ea5a27
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.17.6
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor

[GitHub] camel pull request #1511: CAMEL-10966 Salesforce Maven Plugin Escape Strings

[NickCis]

Github user NickCis closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [VOTE] Release Apache Camel 2.17.6

[Gregor Zurowski]

+1

Thanks,
Gregor


On Sun, Mar 5, 2017 at 2:33 PM, Gregor Zurowski
 wrote:
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.17.6, a new patch release
> that includes 17 fixes and improvements.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12339170=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1068/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1068/org/apache/camel/apache-camel/2.17.6/
>
> Tag: 
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=168e6c362dfeb6166a0b33c28c54027514ea5a27
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.17.6
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor

[GitHub] camel pull request #1515: CAMEL-10963 Correcting getEndpointKey call

[tigertoes]

GitHub user tigertoes opened a pull request:

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

CAMEL-10963 Correcting getEndpointKey call

This should fix the underlying issue (sorry about that!).

I do want to put an integration test much like the others, but I think 
that's best followed up with another PR? Or if you can wait a little bit I can 
produce it as part of this one.

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

$ git pull https://github.com/tigertoes/camel CAMEL-10963

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

https://github.com/apache/camel/pull/1515.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 #1515


commit 737544a428abed2ad9501755efcd64e3ae60c7ee
Author: Tony Tiger 
Date:   2017-03-08T16:15:00Z

CAMEL-10963 Correcting getEndpointKey call




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] camel pull request #1514: CAMEL-10918 create sjms2 component to add support ...

[ryeats]

GitHub user ryeats opened a pull request:

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

CAMEL-10918 create sjms2 component to add support for JMS 2.0

This PR adds a SJMS2 component that can support shared subscriptions along 
with some modifications to the SJMS component so that it could be extended by 
the new SJMS2 component.

I created the branch off of 2.18.x let me know if it should be off master.

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

$ git pull https://github.com/ryeats/camel sjms-sharedconsumer

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

https://github.com/apache/camel/pull/1514.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 #1514


commit 7b5978fbf053abf14c3d4fc21507c027977caf32
Author: Ryan Yeats 
Date:   2017-03-01T22:19:19Z

CAMEL-10918 create sjms2 component to add support for JMS 2.0




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] camel pull request #1513: Camel 10963

[shanekelly-bbc]

Github user shanekelly-bbc closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] camel pull request #1513: Camel 10963

[shanekelly-bbc]

GitHub user shanekelly-bbc opened a pull request:

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

Camel 10963



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

$ git pull https://github.com/shanekelly-bbc/camel CAMEL-10963

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

https://github.com/apache/camel/pull/1513.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 #1513


commit 73e98c2b5dc2dfb487f6836d205a0255de15d60a
Author: Shane Kelly 
Date:   2017-03-08T12:57:21Z

CAMEL-10963 firehose's put request's  deliveryStreamName is now set using 
endpoint.getStreamName();

commit 4a33a5ce98fbd166ef6dbbc1f50892ba198b375b
Author: Shane Kelly 
Date:   2017-03-08T13:12:22Z

CAMEL-10963 adding rought integration test




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] camel pull request #1510: CAMEL-10952 Initial work adding Kinesis Firehose

[tigertoes]

Github user tigertoes closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [VOTE] [CANCEL] Release Apache Camel 2.18.3

[Gregor Zurowski]

Just a short update: I will create the new RC for 2.18.3 later today.
I also plan to release 2.17.6 at the same time.

Thanks,
Gregor


On Tue, Mar 7, 2017 at 9:27 PM, Gregor Zurowski
 wrote:
> This vote is cancelled due to an issue with Spring Boot that has been
> fixed with CAMEL-10951 [1].  I will create a new RC and send out
> another vote e-mail soon.
>
> Thanks,
> Gregor
>
> [1] https://issues.apache.org/jira/browse/CAMEL-10951
>
>
> On Sun, Mar 5, 2017 at 9:07 AM, Gregor Zurowski
>  wrote:
>> Hi Everyone:
>>
>> This is a vote to release Apache Camel 2.18.3, a new patch release
>> that includes 37 fixes and improvements.
>>
>> Release notes: 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12339161=12311211
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachecamel-1067/
>>
>> Tarballs: 
>> https://repository.apache.org/content/repositories/orgapachecamel-1067/org/apache/camel/apache-camel/2.18.3/
>>
>> Tag: 
>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=a1b029f3ca314ac20953f69818c9ae2b07eff4dc
>>
>> Please test this release candidate and cast your vote.
>> [ ] +1 Release the binary as Apache Camel 2.18.3
>> [ ] -1 Veto the release (provide specific comments)
>>
>> The vote is open for at least 72 hours.
>>
>> Thanks,
>> Gregor