Re: [VOTE] Release Apache Camel 4.3.0

[Pascal Schumacher]

+1 (binding)

Thanks!

Am 12.12.2023 um 09:23 schrieb Gregor Zurowski:

Hi Everyone:

This is a vote to release Apache Camel 4.3.0, a new release with 108
new features and improvements. It is the first Camel release that was
built with Java 21.

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

== Apache Camel 4.3.0 ==

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

Tarballs: 
https://repository.apache.org/content/repositories/orgapachecamel-1658/org/apache/camel/apache-camel/4.3.0/

Tag: https://github.com/apache/camel/releases/tag/camel-4.3.0

== Apache Camel Spring Boot 4.3.0 ==

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

Tag: 
https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.3.0

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

The vote is open for at least 72 hours.

Thanks,
Gregor

Re: Camel 4 and camel-activemq

[Pascal Schumacher]

o.k., then I know it is in capable hands. :-)

Thank you very much for working on this.

Cheers,
Pascal

Am 08.05.2023 um 08:34 schrieb Jean-Baptiste Onofré:

Hi Pascal,

I already started to work on this one.

Claus already asked me to do so :)

Regards
JB

On Sun, May 7, 2023 at 11:23 AM Pascal Schumacher
 wrote:

Hi,

guess the camel-activemq component was dropped during the Camel 4
migration because ActiveMQ did not support the jakarta namespace at the
time?

The recent 5.18.0 release of ActiveMQ added jakarta namespace support,
so what about restoring this component?

What do you think?

- Pascal

Re: Camel 4 and camel-activemq

[Pascal Schumacher]

Great!

I am not sure if I will be able to pull it off, but I will give it a try.

Am 07.05.2023 um 12:59 schrieb Claus Ibsen:

Hi

Yes you are welcome to work on that.



On Sun, May 7, 2023 at 11:24 AM Pascal Schumacher 
wrote:


Hi,

guess the camel-activemq component was dropped during the Camel 4
migration because ActiveMQ did not support the jakarta namespace at the
time?

The recent 5.18.0 release of ActiveMQ added jakarta namespace support,
so what about restoring this component?

What do you think?

- Pascal

Camel 4 and camel-activemq

[Pascal Schumacher]

Hi,

guess the camel-activemq component was dropped during the Camel 4
migration because ActiveMQ did not support the jakarta namespace at the
time?

The recent 5.18.0 release of ActiveMQ added jakarta namespace support,
so what about restoring this component?

What do you think?

- Pascal

Re: [VOTE] Release Apache Camel 3.17.0

[Pascal Schumacher]

+1 (binding)

tested with a spring boot app

Thanks Gregor!

Am 16.05.2022 um 09:52 schrieb Gregor Zurowski:

Hi Everyone:

This is a vote to release Apache Camel 3.17.0, a new release with 220
fixes and improvements.

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

== Apache Camel 3.17.0 ==

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

Tarballs: 
https://repository.apache.org/content/repositories/orgapachecamel-1437/org/apache/camel/apache-camel/3.17.0/

Tag: 
https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.17.0

== Apache Camel Spring Boot 3.17.0 ==

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

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.17.0

== Apache Camel Karaf 3.17.0 ==

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

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.17.0

Please test this release candidate and cast your vote:
[ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
Karaf 3.17.0
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Thanks,
Gregor

Re: [VOTE] Release Apache Camel 3.16.0

[Pascal Schumacher]

+1 (binding)

Tested with spring boot. Thanks Gregor!

Am 24.03.2022 um 07:41 schrieb Luca Burgazzoli:

+1 (binding)

---
Luca Burgazzoli


On Thu, Mar 24, 2022 at 4:03 AM Babak Vahdat
 wrote:


+1 (binding)

Tested with own projects. Thanks Gregor!

Babak


On Wed, Mar 23, 2022 at 6:34 PM Gregor Zurowski mailto:gre...@list.zurowski.org>>
wrote:


Hi Everyone:

This is a vote to release Apache Camel 3.16.0, a new minor release
with 206 fixes and improvements.

Release notes:


https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12351219=12311211
<
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12351219=12311211


== Apache Camel 3.16.0 ==

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



Tarballs:


https://repository.apache.org/content/repositories/orgapachecamel-1420/org/apache/camel/apache-camel/3.16.0/
<
https://repository.apache.org/content/repositories/orgapachecamel-1420/org/apache/camel/apache-camel/3.16.0/


Tag:


https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.16.0
<
https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.16.0


== Apache Camel Spring Boot 3.16.0 ==

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



Tag:


https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.16.0
<
https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.16.0


== Apache Camel Karaf 3.16.0 ==

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



Tag:


https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.16.0
<
https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.16.0


Please test this release candidate and cast your vote:
[ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
Karaf 3.16.0
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Thanks,
Gregor

Re: [VOTE] Release Apache Camel 3.15.0

[Pascal Schumacher]

+1 (binding)

Am 01.02.2022 um 07:39 schrieb Gregor Zurowski:

Hi Everyone:

This is a vote to release Apache Camel 3.15.0, a new release with 217
new features and improvements.

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

== Apache Camel 3.15.0 ==

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

Tarballs: 
https://repository.apache.org/content/repositories/orgapachecamel-1407/org/apache/camel/apache-camel/3.15.0/

Tag: 
https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.15.0

== Apache Camel Spring Boot 3.15.0 ==

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

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.15.0

== Apache Camel Karaf 3.15.0 ==

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

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.15.0

Please test this release candidate and cast your vote.

[ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
Karaf 3.15.0
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Thanks,
Gregor

Re: [VOTE] Release Apache Camel 3.14.0 (LTS)

[Pascal Schumacher]

+1 (binding), tested with a spring boot based camel app

Am 13.12.2021 um 13:47 schrieb Gregor Zurowski:

Hi Everyone:

This is a vote to release Apache Camel 3.14.0, a new LTS release with
111 new features and improvements.

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

== Apache Camel 3.14.0 ==

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

Tarballs: 
https://repository.apache.org/content/repositories/orgapachecamel-1380/org/apache/camel/apache-camel/3.14.0/

Tag: 
https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.14.0

== Apache Camel Spring Boot 3.14.0 ==

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

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.14.0

== Apache Camel Karaf 3.14.0 ==

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

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.14.0

Please test this release candidate and cast your vote.

[ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
Karaf 3.14.0
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Thanks,
Gregor

Re: [VOTE] Release Apache Camel 3.13.0

[Pascal Schumacher]

+1 (binding)

Tested with a Spring Boot app.

Thank you Gregor!

Am 09.11.2021 um 08:08 schrieb Gregor Zurowski:

Hi Everyone:

This is a vote to release Apache Camel 3.13.0, a new release with 119
new features and improvements.

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

== Apache Camel 3.13.0 ==

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

Tarballs: 
https://repository.apache.org/content/repositories/orgapachecamel-1371/org/apache/camel/apache-camel/3.13.0/

Tag: 
https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.13.0

== Apache Camel Spring Boot 3.13.0 ==

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

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.13.0

== Apache Camel Karaf 3.13.0 ==

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

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.13.0

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

The vote is open for at least 72 hours.

Thanks,
Gregor

Re: [VOTE] Release Apache Camel 3.12.0

[Pascal Schumacher]

+1 (binding)

successfully tested with a spring-boot app

Am 29.09.2021 um 09:57 schrieb Gregor Zurowski:

Hi Everyone:

This is a vote to release Apache Camel 3.12.0, a new release with 206
new features and improvements.

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

== Apache Camel 3.12.0 ==

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

Tarballs: 
https://repository.apache.org/content/repositories/orgapachecamel-1359/org/apache/camel/apache-camel/3.12.0/

Tag: 
https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.12.0

== Apache Camel Spring Boot 3.12.0 ==

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

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.12.0

== Apache Camel Karaf 3.12.0 ==

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

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.12.0

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

The vote is open for at least 72 hours.

Thanks,
Gregor

Re: [VOTE] Release Apache Camel 3.11.0 (LTS)

[Pascal Schumacher]

+1 (binding)

Am 23.06.2021 um 20:45 schrieb Gregor Zurowski:

Hi Everyone:

This is a vote to release Apache Camel 3.11.0, a new LTS release with
101 improvements and fixes.

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

== Apache Camel 3.11.0 ==

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

Tarballs: 
https://repository.apache.org/content/repositories/orgapachecamel-1336/org/apache/camel/apache-camel/3.11.0/

Tag: 
https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.11.0

== Apache Camel Spring Boot 3.11.0 ==

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

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.11.0

== Apache Camel Karaf 3.11.0 ==

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

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.11.0

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

The vote is open for at least 72 hours.

Thanks,
Gregor

Re: [VOTE] Release Apache Camel 3.10.0 with Spring Boot and Karaf Support Projects

[Pascal Schumacher]

+1 (binding)

Am 17.05.2021 um 09:15 schrieb Gregor Zurowski:

Hi Everyone:

Resending this email as I missed prefixing the subject of the previous
email with VOTE.

This is a vote to release Apache Camel 3.10.0 (with Apache Camel
Spring Boot and Apache Camel Karaf), a new minor release with 208
improvements and fixes.

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

== Apache Camel 3.10.0 ==

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

Tarballs: 
https://repository.apache.org/content/repositories/orgapachecamel-1316/org/apache/camel/apache-camel/3.10.0/

Tag: 
https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.10.0

== Apache Camel Spring Boot 3.10.0 ==

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

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.10.0

== Apache Camel Karaf 3.10.0 ==

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

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.10.0

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

The vote is open for at least 72 hours.

Thanks,
Gregor

Re: Deprecating MDC logging

[Pascal Schumacher]

-0: We are using it a lot. It is very convenient and works great for our
use-cases.

Am 22.03.2021 um 10:45 schrieb Claus Ibsen:

Hi

In Camel 3.x and in a more and more reactive world, then MDC logging
is becoming a more and more bad practice.

That MDC context is thread bound, and that information needs to be
transferred between MDC thread bound context when Camel routes
messages, both within its own routing engine, but also via 3rd party
libraries that uses their threading model.

All that makes MDC not possible to reliably transfer data between
threads, and also to "reset" when its done etc.

Also there is overhead associated with attempting to do this within
the Camel framework.

I would like to deprecate MDC logging in Camel 3.10 onwards.

Re: [HEADS UP] - Modularizing camel-spring

[Pascal Schumacher]

Great new!

Thank you very much!

Am 11.02.2021 um 17:44 schrieb Claus Ibsen:

Hi

The XML DSL has been moved out of camel-spring into its own
camel-spring-xml component.
This makes camel-spring lighter and also for end users that do not use
XML DSL to carry that extra burden/load.

There is more work to do for camel-spring-boot to move out its XML DSL
support into a new camel-spring-boot-xml module.

The JIRA ticket is
https://issues.apache.org/jira/browse/CAMEL-16170

Re: [VOTE] Release Apache Camel 3.8.0 with Spring Boot and Karaf Support Projects

[Pascal Schumacher]

+1

successfully upgraded some camel-spring-boot based projects

Am 10.02.2021 um 08:52 schrieb Gregor Zurowski:

Hi Everyone:

This is a vote to release Apache Camel 3.8.0 (with Apache Camel Spring
Boot and Apache Camel Karaf), a new minor release with 160
improvements and fixes.

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

== Apache Camel 3.8.0 ==

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

Tarballs: 
https://repository.apache.org/content/repositories/orgapachecamel-1286/org/apache/camel/apache-camel/3.8.0/

Tag: 
https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.8.0

== Apache Camel Spring Boot 3.8.0 ==

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

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.8.0

== Apache Camel Karaf 3.8.0 ==

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

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.8.0

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

The vote is open for at least 72 hours.

Thanks,
Gregor

Re: [VOTE] Release Apache Camel 3.4.0 with Spring Boot and Karaf Support Projects

[Pascal Schumacher]

+1 (binding)

Thanks you very much Gregor!


Am 16.06.2020 um 22:04 schrieb Zoran Regvart:

+1 (binding)

Thanks Gregor!

zoran

On Mon, Jun 15, 2020 at 9:15 AM Gregor Zurowski
 wrote:

Hi Everyone:

This is a vote to release Apache Camel 3.4.0 (with Apache Camel Spring
Boot and Apache Camel Karaf), a new minor release with 118
improvements and fixes.

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

== Apache Camel 3.4.0 ==

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

Tarballs: 
https://repository.apache.org/content/repositories/orgapachecamel-1220/org/apache/camel/apache-camel/3.4.0/

Tag: 
https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.4.0

== Apache Camel Spring Boot 3.4.0 ==

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

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.4.0

== Apache Camel Karaf 3.4.0 ==

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

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.4.0

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

The vote is open for at least 72 hours.

Thanks,
Gregor

Re: [VOTE] Release Apache Camel 3.3.0 with Spring Boot and Karaf Support Projects

[Pascal Schumacher]

+1 (binding)

Am 12.05.2020 um 09:34 schrieb Nicola Ferraro:

+1 (binding)

Nicola

On Tue, May 12, 2020 at 7:45 AM Luca Burgazzoli 
wrote:


+1 (binding)

---
Luca Burgazzoli


On Tue, May 12, 2020 at 7:19 AM Claus Ibsen  wrote:


+1 (binding)

On Mon, May 11, 2020 at 12:49 PM Gregor Zurowski
 wrote:

Hi Everyone:

This is a vote to release Apache Camel 3.3.0 (with Apache Camel Spring
Boot and Apache Camel Karaf), a new minor release with 149
improvements and fixes.

Release notes:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12347798=12311211

== Apache Camel 3.3.0 ==

Staging repository:


https://repository.apache.org/content/repositories/orgapachecamel-1211/

Tarballs:

https://repository.apache.org/content/repositories/orgapachecamel-1211/org/apache/camel/apache-camel/3.3.0/

Tag:

https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.3.0

== Apache Camel Spring Boot 3.3.0 ==

Staging repository:


https://repository.apache.org/content/repositories/orgapachecamel-1213/

Tag:

https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.3.0

== Apache Camel Karaf 3.3.0 ==

Staging repository:


https://repository.apache.org/content/repositories/orgapachecamel-1212/

Tag:

https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.3.0

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

The vote is open for at least 72 hours.

Thanks,
Gregor



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

Camel github notifications send to dev list

[Pascal Schumacher]

Since the beginning of this week github notifications for camel are send
to this mailing list instead of the commits mailing list, e.g.

E.g.
https://mail-archives.apache.org/mod_mbox/camel-dev/202004.mbox/%3Ccamel.3762.MDExOlB1bGxSZXF1ZXN0NDA2MDQxMzY0.gitbox%40gitbox.apache.org%3E


Therefore I created https://issues.apache.org/jira/browse/INFRA-20178

Infra suggested that we add a |.asf.yaml| file to configure it our-self
(see:
https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories
for configuration options.)

So I created https://github.com/apache/camel/pull/3773

Cheers,

Pascal

Re: Merge Commits?

[Pascal Schumacher]

Thank you very much!

Am 17.04.2020 um 15:56 schrieb Andrea Cosentino:

We have now only squash and merge and rebase and merge enabled on

camel
camel-karaf
camel-spring-boot

--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Friday, April 17, 2020, 11:40:19 AM GMT+2, Omar Al-Safi  
wrote:





Thanks Andrea!

On Fri, Apr 17, 2020 at 11:36 AM Andrea Cosentino 
 wrote:

https://issues.apache.org/jira/browse/INFRA-20137

--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Thursday, April 16, 2020, 06:07:18 PM GMT+2, David Jencks 
 wrote:





Thanks!
David Jencks


On Apr 16, 2020, at 8:56 AM, Andrea Cosentino  wrote:

This is something only INFRA could setup.

I think it's not something critical, I'll raise an issue to INFRA anyway.

Il giorno gio 16 apr 2020 alle ore 17:54 David Jencks <
david.a.jen...@gmail.com> ha scritto:


Lets not let this drop on the floor and get forgotten…

The instructions for enabling and requiring rebase-and-merge for PRs are
here:
https://help.github.com/en/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests

I don’t appear to have the permissions to set this up…. who does?

Does anyone know if there are equivalent options/settings for the apache
git repo?

Thanks
David Jencks


On Apr 15, 2020, at 10:22 PM, David Jencks 

wrote:

Hi Claus,

I think that sometimes more than one commit is appropriate for a PR.

For instance some of mine recently have consisted of a few lines change of
generation code and hundreds of files changed as a result.  It’s much
clearer if those are two separate commits.  Also, my impression is that the
project settings have the GitHub button be just “merge” without squash.

I’ve been waiting for review of my PRs which means it’s extremely likely

that master will have progressed since my push.  So I think the project
rebase and push setting will be a real help.

Thanks
David Jencks


On Apr 15, 2020, at 10:00 PM, Claus Ibsen 

wrote:

Hi

Yes we should do rebase and merge, or squash and merge style, so its

linear.

On github the green button is default for "squash and merge".

I always do git pull --rebase from CLI before pushing, so my commits
are added on top of the branch.



On Wed, Apr 15, 2020 at 10:09 PM Pascal Schumacher
 wrote:

Hi,

recently there were several merge commits (especially for merged pull
request).

I thought the consensus was to avoid merge commits to keep the git
history as clean as possible.

Should we keep this policy?

What do you think?

Cheers,

Pascal




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

Merge Commits?

[Pascal Schumacher]

Hi,

recently there were several merge commits (especially for merged pull
request).

I thought the consensus was to avoid merge commits to keep the git
history as clean as possible.

Should we keep this policy?

What do you think?

Cheers,

Pascal

Remove the "jdk9+-build" maven profile?

[Pascal Schumacher]

Hi,

what do you think about removing the "jdk9+-build" profile in the parent
pom which adds a lot of JAXB/SOAP etc. related dependencies?

When I remove this profile and try to build on Java I get no further
than the "camel-api" module:

[ERROR]
/camel/core/camel-api/src/main/java/org/apache/camel/ExchangePattern.java:[19,32]
error: package javax.xml.bind.annotation does not exist
[ERROR]
/camel/core/camel-api/src/main/java/org/apache/camel/ExchangePattern.java:[20,32]
error: package javax.xml.bind.annotation does not exist
[ERROR]
/camel/core/camel-api/src/main/java/org/apache/camel/ExchangePattern.java:[25,1]
error: cannot find symbol
[ERROR]   symbol: class XmlType
[ERROR]
/camel/core/camel-api/src/main/java/org/apache/camel/ExchangePattern.java:[26,1]
error: cannot find symbol

[ERROR]   symbol: class XmlEnum

..

Or should this wait until Camel requires Java 11?

Cheers,

Pascal

Re: [camel] 01/02: Switch to faster String#indexOf method taking a char parameter.

[Pascal Schumacher]

Yes, the commit I committed this morning did not compile (saw your mail).

Sorry about that. :(

The reason were these PackageHelper changes:

https://github.com/apache/camel/commit/93e11b338ca61415a84c500622ac8f7a2024ce99#diff-e589ec19f41e386bd5611b12566203af

The new commit does not contain these changes.





Am 06.04.2020 um 20:42 schrieb Andrea Cosentino:

This doesn't compile. At least this morning with jdk8

Il lun 6 apr 2020, 20:33  ha scritto:


This is an automated email from the ASF dual-hosted git repository.

pascalschumacher pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git

commit f742967176a8c8313645d2091d53071ece42c104
Author: Pascal Schumacher 
AuthorDate: Mon Apr 6 20:30:15 2020 +0200

 Switch to faster String#indexOf method taking a char parameter.
---
  .../src/main/java/org/apache/camel/parser/RouteBuilderParser.java | 2 +-
  .../src/main/java/org/apache/camel/parser/XmlRouteParser.java | 2 +-
  .../component/aws/xray/decorators/AbstractSegmentDecorator.java   | 6
+++---
  .../camel/component/aws/xray/component/TestXRayProducer.java  | 2 +-
  .../main/java/org/apache/camel/language/bean/BeanLanguage.java| 2 +-
  .../java/org/apache/camel/dataformat/bindy/UnicodeHelperTest.java | 8

  .../java/org/apache/camel/component/cxf/jaxrs/CxfRsProducer.java  | 4 ++--
  .../java/org/apache/camel/component/dozer/ExpressionMapper.java   | 4 ++--
  .../java/org/apache/camel/component/file/remote/FtpComponent.java | 4 ++--
  .../org/apache/camel/component/file/remote/SftpComponent.java | 2 +-
  .../google/bigquery/sql/GoogleBigQuerySQLConfiguration.java   | 2 +-
  .../src/main/java/org/apache/camel/http/base/HttpHelper.java  | 2 +-
  .../src/main/java/org/apache/camel/http/common/HttpHelper.java| 2 +-
  .../main/java/org/apache/camel/component/http/HttpProducer.java   | 2 +-
  .../java/org/apache/camel/component/irc/IrcConfiguration.java | 2 +-
  .../main/java/org/apache/camel/component/scp/ScpComponent.java| 2 +-
  .../java/org/apache/camel/component/mail/MailConfiguration.java   | 2 +-
  .../org/apache/camel/component/milo/AbstractMiloServerTest.java   | 2 +-
  .../org/apache/camel/component/netty/http/NettyHttpHelper.java| 2 +-
  .../main/java/org/apache/camel/component/rest/RestProducer.java   | 4 ++--
  .../salesforce/internal/streaming/SubscriptionHelper.java | 2 +-
  .../org/apache/camel/component/websocket/WebsocketComponent.java  | 8

  .../camel/component/zookeeper/operations/ZooKeeperHelper.java | 2 +-
  .../java/org/apache/camel/catalog/impl/AbstractCamelCatalog.java  | 6
+++---
  .../src/main/java/org/apache/camel/impl/RouteIdFactory.java   | 2 +-
  .../java/org/apache/camel/builder/xml/XPathTransformTest.java | 2 +-
  .../src/main/java/org/apache/camel/main/BaseMainSupport.java  | 4 ++--
  .../src/main/java/org/apache/camel/support/ResourceHelper.java| 2 +-
  .../src/main/java/org/apache/camel/xml/io/XmlStreamReader.java| 6
+++---
  .../src/test/java/org/apache/camel/xml/in/ModelParserTest.java| 2 +-
  .../main/java/org/apache/camel/maven/packaging/XRefCheckMojo.java | 4 ++--
  31 files changed, 49 insertions(+), 49 deletions(-)

diff --git
a/catalog/camel-route-parser/src/main/java/org/apache/camel/parser/RouteBuilderParser.java
b/catalog/camel-route-parser/src/main/java/org/apache/camel/parser/RouteBuilderParser.java
index 76d51e1..af5bb24 100644
---
a/catalog/camel-route-parser/src/main/java/org/apache/camel/parser/RouteBuilderParser.java
+++
b/catalog/camel-route-parser/src/main/java/org/apache/camel/parser/RouteBuilderParser.java
@@ -432,7 +432,7 @@ public final class RouteBuilderParser {

  private static String endpointComponentName(String uri) {
  if (uri != null) {
-int idx = uri.indexOf(":");
+int idx = uri.indexOf(':');
  if (idx > 0) {
  return uri.substring(0, idx);
  }
diff --git
a/catalog/camel-route-parser/src/main/java/org/apache/camel/parser/XmlRouteParser.java
b/catalog/camel-route-parser/src/main/java/org/apache/camel/parser/XmlRouteParser.java
index 1c1f9d3..e1a2cb0 100644
---
a/catalog/camel-route-parser/src/main/java/org/apache/camel/parser/XmlRouteParser.java
+++
b/catalog/camel-route-parser/src/main/java/org/apache/camel/parser/XmlRouteParser.java
@@ -308,7 +308,7 @@ public final class XmlRouteParser {

  private static String endpointComponentName(String uri) {
  if (uri != null) {
-int idx = uri.indexOf(":");
+int idx = uri.indexOf(':');
  if (idx > 0) {
  return uri.substring(0, idx);
  }
diff --git
a/components/camel-aws-xray/src/main/java/org/apache/camel/component/aws/xray/decorators/AbstractSegmentDecorator.java
b/components/camel-aws-xray/src/main/java/org/apache/camel/component/aws/xray/decorators/AbstractSegmentDecorator.java
ind

3.x Upgrade Guide Order

[Pascal Schumacher]

Hi,

currently the 3.x Upgrade Guide
(https://camel.apache.org/manual/latest/camel-3x-upgrade-guide.html) is
confusing, because some information on the 3.2 upgrade is before the 3.1
upgrade while most of it is after the 3.1 upgrade.

In my opinion it would be helpful if the guide was sorted in descending
order by version.

What do you think?

Pascal

Re: [camel] branch master updated: Update Commons Compress to version 1.20.

[Pascal Schumacher]

Reverted it.

Sorry,

Pascal


Am 30.03.2020 um 21:48 schrieb Andrea Cosentino:

This breaks some tests in tarfile component I guess

Il lun 30 mar 2020, 21:42  ha scritto:


This is an automated email from the ASF dual-hosted git repository.

pascalschumacher pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/master by this push:
  new 1decde2  Update Commons Compress to version 1.20.
1decde2 is described below

commit 1decde25348bbc8c012edd1cb6eb20898457c7bb
Author: Pascal Schumacher 
AuthorDate: Mon Mar 30 21:39:49 2020 +0200

 Update Commons Compress to version 1.20.
---
  parent/pom.xml | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/parent/pom.xml b/parent/pom.xml
index df266c6..9ec5101 100644
--- a/parent/pom.xml
+++ b/parent/pom.xml
@@ -108,7 +108,7 @@
  1.14
  3.2.2
  4.4
-1.19
+1.20
  1.9

  2.7
  1.6

Apache Http Client 5 based http component?

[Pascal Schumacher]

Hi,

Apache HttpComponents Client 5.0 was released last month (see:
https://hc.apache.org/news.html).

Package names and a lot of class and method names were changed.

As Camel allows users to customize Http Client usage and this exposes
Http Client 4 classes, I believe a new component should be created
(instead of updating the existing one).

I started to have a look at creating an new http5 component based on
Apache Http Client 5 (not sure if I would be able to do it) .

When camel moves to Java 11 (not sure when that will be) there are plans
to implement an http component based on the Java (JDK) http client (see:
https://issues.apache.org/jira/browse/CAMEL-14660).

So the question is: Does it make sense to invest more time into this or
is it a waste of time?

What do you think?

-Pascal

Re: Closing Down on Apache Camel 3.1 (Groovy 3.0.1 Update)

[Pascal Schumacher]

Normally I would not have done the update with an release in progress,
but as the Groovy 3.0.0 was missing JKD9 classes (see:
https://mail-archives.apache.org/mod_mbox/groovy-dev/202002.mbox/%3CCAMbkE7RY7cRKD1HgwymRT1peV1YPD_9fO5DZt6%3DCfQT%2Bj-Ns6Q%40mail.gmail.com%3E)

and 3.0.1 contains only very few other changes:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12346968

I thought we should update.

Am 18.02.2020 um 20:22 schrieb Andrea Cosentino:

There is also a groovy update today btw. Can you check with version 3.0.0?

Re: R: Re: NOISE in @dev from PRs

[Pascal Schumacher]

Thank you very much!

Am 12.02.2020 um 21:14 schrieb Andrea Cosentino:

It should be fixed

Inviato da Yahoo Mail su Android

   Il mer, 12 feb, 2020 alle 17:28, Andrea Cosentino ha 
scritto:   https://issues.apache.org/jira/browse/INFRA-19850

Il giorno mer 12 feb 2020 alle ore 17:12 Pascal Schumacher <
pascalschumac...@gmx.net> ha scritto:


+1, another source is camel-examples

Am 12.02.2020 um 05:43 schrieb Claus Ibsen:

Hi

We have noise again in this @dev mailing list now from
camel-spring-boot and camel-kafka-connector sub projects.

Can we get these turned off like we did for main Camel. So the @dev is
ONLY for human emails.

Re: NOISE in @dev from PRs

[Pascal Schumacher]

+1, another source is camel-examples

Am 12.02.2020 um 05:43 schrieb Claus Ibsen:

Hi

We have noise again in this @dev mailing list now from
camel-spring-boot and camel-kafka-connector sub projects.

Can we get these turned off like we did for main Camel. So the @dev is
ONLY for human emails.

camel-spring-boot: Snapshot artifacts no longer available?

[Pascal Schumacher]

Hi,

after the Camel Spring Boot artifacts where moved into a separate
repository it looks like snapshot artifacts are no longer published to
the Apache Foundation Maven repository.

What do you think about restoring the publication?

Thanks,

Pascal

Re: camel-spring-boot: Disable JMX by default?

[Pascal Schumacher]

If removing the dependency is enough to disable it I think we should
just remove the dependency.

I created https://issues.apache.org/jira/browse/CAMEL-14481

Thanks,
Pascal

Am 03.02.2020 um 10:11 schrieb Claus Ibsen:

Hi

Ah okay, yeah we should likely remove camel-management as a dependency
for camel-spring-boot, then JMX is disabled out of the box.
And maybe even also set the configuration option to false. But then to
enable it you need both to add the JAR and set the option to true

Can you create a JIRA.

On Sun, Feb 2, 2020 at 11:39 PM Pascal Schumacher
 wrote:

Am 02.02.2020 um 18:29 schrieb Claus Ibsen:

Hi

This is only Spring Boot JMX, and spring boot may not have so much
data in JMX that anybody are using it.

Yes, Spring Boot does not offer as much JMX data as Camel. On the flip
side Camel JMX needs more memory (as far as I remember, haven't checked
recently).

Other than Spring JMX (and JMX for Spring Components like Spring Batch
and Spring Integration) Spring Boot 2.2 also disabled Tomcat JMX by
default (see: https://github.com/spring-projects/spring-boot/issues/16498).


But I see the point, but what Camel does in 3.x is to make JMX
optional if you have camel-management on the classpath or not.
And of course allows to configure this as well with those options.

Can you check the 3.0 spring boot example and see if camel-management
gets added out of the box or not?
We may have added it specially for camel-spring-boot to make it JMX
out of the box.

Yes, camel-spring-boot has a compile camel-management dependency, so it
is added out of the box.

-Pascal

Re: camel-spring-boot: Disable JMX by default?

[Pascal Schumacher]

Am 02.02.2020 um 18:29 schrieb Claus Ibsen:

Hi

This is only Spring Boot JMX, and spring boot may not have so much
data in JMX that anybody are using it.


Yes, Spring Boot does not offer as much JMX data as Camel. On the flip
side Camel JMX needs more memory (as far as I remember, haven't checked
recently).

Other than Spring JMX (and JMX for Spring Components like Spring Batch
and Spring Integration) Spring Boot 2.2 also disabled Tomcat JMX by
default (see: https://github.com/spring-projects/spring-boot/issues/16498).


But I see the point, but what Camel does in 3.x is to make JMX
optional if you have camel-management on the classpath or not.
And of course allows to configure this as well with those options.

Can you check the 3.0 spring boot example and see if camel-management
gets added out of the box or not?
We may have added it specially for camel-spring-boot to make it JMX
out of the box.


Yes, camel-spring-boot has a compile camel-management dependency, so it
is added out of the box.

-Pascal

camel-spring-boot: Disable JMX by default?

[Pascal Schumacher]

Hi,

Spring Boot 2.2 disables JMX by default (see:
https://github.com/spring-projects/spring-boot/issues/16090).

Should we follow suit and change the default of spring-boot?

What do you think?

-Pascal

Re: camel-spring-boot: Disable proxying of bean methods for auto-configuration classes?

[Pascal Schumacher]

I have created https://issues.apache.org/jira/browse/CAMEL-14471 and
https://github.com/apache/camel-spring-boot/pull/3 to track this change.

camel-spring-boot: Disable proxying of bean methods for auto-configuration classes?

[Pascal Schumacher]

Hi Cameleers,

Spring 5.2 makes it possible to disable proxying of bean methods for
configuration classes (with @Configuration(proxyBeanMethods=false)) to
avoid the generation of cglib proxies and improve performance. For
details see:
https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Configuration.html#proxyBeanMethods--

Spring Boot (see:
https://github.com/spring-projects/spring-boot/issues/9068) and other
Spring projects already use this for their autoconfiguration classes.

I think camel-spring-boot could also use this, or am I missing something?

What do you think?

-Pascal

Re: [ANNOUNCEMENT] Apache Camel 3.0.1 Released

[Pascal Schumacher]

Thank you very much!

Looks like they fixed it. I was just able to download all the necessary
3.0.1 dependencies from maven central.

Am 18.01.2020 um 19:52 schrieb David Karlsen:

I've opened https://issues.sonatype.org/browse/MVNCENTRAL-5483

lør. 18. jan. 2020 kl. 13:44 skrev Andrea Cosentino :


The only workaround is using Apache repository.

Il sab 18 gen 2020, 13:36 Pascal Schumacher  ha
scritto:


Thanks for the update!

Spring-boot-dependencies now work, but



https://repo1.maven.org/maven2/org/apache/camel/camel-parent/3.0.1/camel-parent-3.0.1.pom

still returns 404 for me :(.

Am 18.01.2020 um 11:53 schrieb Gregor Zurowski:

Another update from Sonatype: The previous CDN issues are resolved.

Thanks,
Gregor

On Fri, Jan 17, 2020 at 8:20 PM Gregor Zurowski
 wrote:

I just received an update from Sonatype that they are still working on
the CDN issues. At this point the only option is to manually fix those
issues on their side until they have a working fix.

On Fri, Jan 17, 2020 at 4:26 PM Pascal Schumacher
 wrote:

https://repo1.maven.org/maven2/org/apache/camel/springboot/camel-spring-boot-dependencies/3.0.1/camel-spring-boot-dependencies-3.0.1.pom

still returns 404 for me, while



https://repo1.maven.org/maven2/org/apache/camel/springboot/camel-spring-boot-dependencies/3.0.0/camel-spring-boot-dependencies-3.0.0.pom

works.

Am 17.01.2020 um 15:37 schrieb Gregor Zurowski:

I just received an update that the problem should be resolved by

now.

I've checked with


https://repo1.maven.org/maven2/org/apache/camel/camel/3.0.1/camel-3.0.1.pom

and it's working now.

Please let me know if you experience issues with any other Camel

artifacts.

Thanks,
Gregor


On Fri, Jan 17, 2020 at 3:04 PM Andrea Cosentino <

ancosen1...@yahoo.com> wrote:

As a workaround the users can point to Apache repository

--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Friday, January 17, 2020, 9:48:17 AM GMT+1, Gregor Zurowski <

gre...@list.zurowski.org> wrote:





Not yet, latest response I got from them was yesterday and they

were

still working on it. I will send an update as soon as I have any

news.

Thanks,
Gregor



On Fri, Jan 17, 2020 at 8:34 AM Andrea Cosentino
 wrote:

Gregor, good morning. Do you have any news? We have others

reporter

actually on Twitter

https://twitter.com/chicchiricco/status/1218064667144261632

It seems a wider problem.

Thank you

--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Thursday, January 16, 2020, 5:32:47 PM GMT+1, Gregor Zurowski <

gre...@list.zurowski.org> wrote:





Great that it's working now for the BOM, but there still seem to

be

issues with other of our POMs. I actually reached out to my

contacts

at Sonatype earlier today and hope they will find a working

solution

for all artifacts.

Thanks,
Gregor

On Thu, Jan 16, 2020 at 4:58 PM David Karlsen <

davidkarl...@gmail.com> wrote:

Sonatype fixed it
https://twitter.com/sonatype_ops/status/1217837055306354688?s=20

tor. 16. jan. 2020 kl. 14:26 skrev Gregor Zurowski <

gre...@list.zurowski.org

:
That's weird, seems to be a caching issue as I get the correct

file

when I add a query string to the URL:



https://repo1.maven.org/maven2/org/apache/camel/camel-bom/3.0.1/camel-bom-3.0.1.pom?tes


On Thu, Jan 16, 2020 at 1:03 PM Andrea Cosentino <

anco...@gmail.com>

wrote:

Gregor, can you double check? It seems we don't have the pom

for

camel-bom.

Il giorno gio 16 gen 2020 alle ore 12:52 David Karlsen <
davidkarl...@gmail.com> ha scritto:


I get a 404 on



https://repo1.maven.org/maven2/org/apache/camel/camel-bom/3.0.1/camel-bom-3.0.1.pom

tor. 16. jan. 2020 kl. 09:47 skrev Gregor Zurowski <
gre...@list.zurowski.org

:
The Camel community announces the immediate availability of

the Camel

3.0.1 patch release. This is the first patch release for the

Camel

3.0.x branch and contains 41 fixes and improvements applied

in

the

past weeks by the community.

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] https://camel.apache.org/releases/release-3.0.1/
[3]


https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12346544=12311211

--
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen


--
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen

Re: [ANNOUNCEMENT] Apache Camel 3.0.1 Released

[Pascal Schumacher]

Thanks for the update!

Spring-boot-dependencies now work, but
https://repo1.maven.org/maven2/org/apache/camel/camel-parent/3.0.1/camel-parent-3.0.1.pom
still returns 404 for me :(.

Am 18.01.2020 um 11:53 schrieb Gregor Zurowski:

Another update from Sonatype: The previous CDN issues are resolved.

Thanks,
Gregor

On Fri, Jan 17, 2020 at 8:20 PM Gregor Zurowski
 wrote:

I just received an update from Sonatype that they are still working on
the CDN issues. At this point the only option is to manually fix those
issues on their side until they have a working fix.

On Fri, Jan 17, 2020 at 4:26 PM Pascal Schumacher
 wrote:

https://repo1.maven.org/maven2/org/apache/camel/springboot/camel-spring-boot-dependencies/3.0.1/camel-spring-boot-dependencies-3.0.1.pom

still returns 404 for me, while

https://repo1.maven.org/maven2/org/apache/camel/springboot/camel-spring-boot-dependencies/3.0.0/camel-spring-boot-dependencies-3.0.0.pom

works.

Am 17.01.2020 um 15:37 schrieb Gregor Zurowski:

I just received an update that the problem should be resolved by now.
I've checked with
https://repo1.maven.org/maven2/org/apache/camel/camel/3.0.1/camel-3.0.1.pom
and it's working now.

Please let me know if you experience issues with any other Camel artifacts.

Thanks,
Gregor


On Fri, Jan 17, 2020 at 3:04 PM Andrea Cosentino  wrote:

As a workaround the users can point to Apache repository

--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Friday, January 17, 2020, 9:48:17 AM GMT+1, Gregor Zurowski 
 wrote:





Not yet, latest response I got from them was yesterday and they were
still working on it. I will send an update as soon as I have any news.

Thanks,
Gregor



On Fri, Jan 17, 2020 at 8:34 AM Andrea Cosentino
 wrote:

Gregor, good morning. Do you have any news? We have others reporter actually on 
Twitter

https://twitter.com/chicchiricco/status/1218064667144261632

It seems a wider problem.

Thank you

--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Thursday, January 16, 2020, 5:32:47 PM GMT+1, Gregor Zurowski 
 wrote:





Great that it's working now for the BOM, but there still seem to be
issues with other of our POMs. I actually reached out to my contacts
at Sonatype earlier today and hope they will find a working solution
for all artifacts.

Thanks,
Gregor

On Thu, Jan 16, 2020 at 4:58 PM David Karlsen  wrote:

Sonatype fixed it
https://twitter.com/sonatype_ops/status/1217837055306354688?s=20

tor. 16. jan. 2020 kl. 14:26 skrev Gregor Zurowski 
:
That's weird, seems to be a caching issue as I get the correct file
when I add a query string to the URL:

https://repo1.maven.org/maven2/org/apache/camel/camel-bom/3.0.1/camel-bom-3.0.1.pom?tes


On Thu, Jan 16, 2020 at 1:03 PM Andrea Cosentino 
wrote:

Gregor, can you double check? It seems we don't have the pom for

camel-bom.

Il giorno gio 16 gen 2020 alle ore 12:52 David Karlsen <
davidkarl...@gmail.com> ha scritto:


I get a 404 on



https://repo1.maven.org/maven2/org/apache/camel/camel-bom/3.0.1/camel-bom-3.0.1.pom

tor. 16. jan. 2020 kl. 09:47 skrev Gregor Zurowski <
gre...@list.zurowski.org

:
The Camel community announces the immediate availability of the Camel
3.0.1 patch release. This is the first patch release for the Camel
3.0.x branch and contains 41 fixes and improvements applied in the
past weeks by the community.

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] https://camel.apache.org/releases/release-3.0.1/
[3]


https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12346544=12311211

--
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen


--
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen

Re: [ANNOUNCEMENT] Apache Camel 3.0.1 Released

[Pascal Schumacher]

https://repo1.maven.org/maven2/org/apache/camel/springboot/camel-spring-boot-dependencies/3.0.1/camel-spring-boot-dependencies-3.0.1.pom

still returns 404 for me, while

https://repo1.maven.org/maven2/org/apache/camel/springboot/camel-spring-boot-dependencies/3.0.0/camel-spring-boot-dependencies-3.0.0.pom

works.

Am 17.01.2020 um 15:37 schrieb Gregor Zurowski:

I just received an update that the problem should be resolved by now.
I've checked with
https://repo1.maven.org/maven2/org/apache/camel/camel/3.0.1/camel-3.0.1.pom
and it's working now.

Please let me know if you experience issues with any other Camel artifacts.

Thanks,
Gregor


On Fri, Jan 17, 2020 at 3:04 PM Andrea Cosentino  wrote:

As a workaround the users can point to Apache repository

--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Friday, January 17, 2020, 9:48:17 AM GMT+1, Gregor Zurowski 
 wrote:





Not yet, latest response I got from them was yesterday and they were
still working on it. I will send an update as soon as I have any news.

Thanks,
Gregor



On Fri, Jan 17, 2020 at 8:34 AM Andrea Cosentino
 wrote:

Gregor, good morning. Do you have any news? We have others reporter actually on 
Twitter

https://twitter.com/chicchiricco/status/1218064667144261632

It seems a wider problem.

Thank you

--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Thursday, January 16, 2020, 5:32:47 PM GMT+1, Gregor Zurowski 
 wrote:





Great that it's working now for the BOM, but there still seem to be
issues with other of our POMs. I actually reached out to my contacts
at Sonatype earlier today and hope they will find a working solution
for all artifacts.

Thanks,
Gregor

On Thu, Jan 16, 2020 at 4:58 PM David Karlsen  wrote:

Sonatype fixed it
https://twitter.com/sonatype_ops/status/1217837055306354688?s=20

tor. 16. jan. 2020 kl. 14:26 skrev Gregor Zurowski 
:
That's weird, seems to be a caching issue as I get the correct file
when I add a query string to the URL:

https://repo1.maven.org/maven2/org/apache/camel/camel-bom/3.0.1/camel-bom-3.0.1.pom?tes


On Thu, Jan 16, 2020 at 1:03 PM Andrea Cosentino 
wrote:

Gregor, can you double check? It seems we don't have the pom for

camel-bom.

Il giorno gio 16 gen 2020 alle ore 12:52 David Karlsen <
davidkarl...@gmail.com> ha scritto:


I get a 404 on



https://repo1.maven.org/maven2/org/apache/camel/camel-bom/3.0.1/camel-bom-3.0.1.pom

tor. 16. jan. 2020 kl. 09:47 skrev Gregor Zurowski <
gre...@list.zurowski.org

:
The Camel community announces the immediate availability of the Camel
3.0.1 patch release. This is the first patch release for the Camel
3.0.x branch and contains 41 fixes and improvements applied in the
past weeks by the community.

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] https://camel.apache.org/releases/release-3.0.1/
[3]


https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12346544=12311211


--
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen



--
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen

Re: Links from Github commits to Apache Jira Issues

[Pascal Schumacher]

Feature was enable by infra a few hours ago and works:

https://github.com/apache/camel/commits/master

Cheers,
Pascal

Am 10.01.2020 um 17:25 schrieb Zoran Regvart:

Hi Pascal,
I think it's this feature that's available only on GitHub Enterprise plan:

https://help.github.com/en/github/administering-a-repository/configuring-autolinks-to-reference-external-resources

zoran

On Fri, Jan 10, 2020 at 3:30 PM Pascal Schumacher
 wrote:

Yes, I also prefer the no-braces style.

As I wasn't able to find any documentation on how to enable this feature
I created a infra ticket:

https://issues.apache.org/jira/browse/INFRA-19699


Am 10.01.2020 um 10:01 schrieb Andrea Cosentino:

Yeah, it would be handy, but please no brackets.

--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Friday, January 10, 2020, 9:59:42 AM GMT+1, Claus Ibsen 
 wrote:





Hi

Yeah this would be nice. The pattern should match the style without
the hard brackets too, eg just CAMEL-12345: foo bar blah blah

On Fri, Jan 10, 2020 at 9:40 AM Zoran Regvart  wrote:

+1

Well spotted Pascal, that would come in handy.

zoran

On Thu, Jan 9, 2020 at 10:10 PM Pascal Schumacher
 wrote:

Hi,

recently noticed that Maven commits mentioning Jira issues contain links
to the Apache Jira Issue, see:

https://github.com/apache/maven/commits/master

The same goes for pull request commits (e.g.
https://github.com/apache/maven/pull/312/commits).

In my opinion this is quite handy.

What do you think about enabling this for Camel?

(I believe it has be enabled by infra, because it does not work for
https://github.com/apache/camel/pull/3472/commits).

-Pascal


--
Zoran Regvart

Re: Links from Github commits to Apache Jira Issues

[Pascal Schumacher]

Yes, I also prefer the no-braces style.

As I wasn't able to find any documentation on how to enable this feature
I created a infra ticket:

https://issues.apache.org/jira/browse/INFRA-19699


Am 10.01.2020 um 10:01 schrieb Andrea Cosentino:

Yeah, it would be handy, but please no brackets.

--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Friday, January 10, 2020, 9:59:42 AM GMT+1, Claus Ibsen 
 wrote:





Hi

Yeah this would be nice. The pattern should match the style without
the hard brackets too, eg just CAMEL-12345: foo bar blah blah

On Fri, Jan 10, 2020 at 9:40 AM Zoran Regvart  wrote:

+1

Well spotted Pascal, that would come in handy.

zoran

On Thu, Jan 9, 2020 at 10:10 PM Pascal Schumacher
 wrote:

Hi,

recently noticed that Maven commits mentioning Jira issues contain links
to the Apache Jira Issue, see:

https://github.com/apache/maven/commits/master

The same goes for pull request commits (e.g.
https://github.com/apache/maven/pull/312/commits).

In my opinion this is quite handy.

What do you think about enabling this for Camel?

(I believe it has be enabled by infra, because it does not work for
https://github.com/apache/camel/pull/3472/commits).

-Pascal



--
Zoran Regvart

Links from Github commits to Apache Jira Issues

[Pascal Schumacher]

Hi,

recently noticed that Maven commits mentioning Jira issues contain links
to the Apache Jira Issue, see:

https://github.com/apache/maven/commits/master

The same goes for pull request commits (e.g.
https://github.com/apache/maven/pull/312/commits).

In my opinion this is quite handy.

What do you think about enabling this for Camel?

(I believe it has be enabled by infra, because it does not work for
https://github.com/apache/camel/pull/3472/commits).

-Pascal

Re: [camel] branch master updated: FastjsonDataFormat: Use the build serializerFeatureList to configure FastJson.

[Pascal Schumacher]

Sorry for breaking the build by using a Java 11 method.

Am 20.12.2019 um 17:11 schrieb Andrea Cosentino:

Sorry but I had to revert, the JDK8 build is broken.

Il giorno ven 20 dic 2019 alle ore 15:22  ha
scritto:


This is an automated email from the ASF dual-hosted git repository.

pascalschumacher pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/master by this push:
  new 56496e5  FastjsonDataFormat: Use the build serializerFeatureList
to configure FastJson.
56496e5 is described below

commit 56496e5233f32cd2aff9f79384888b175f9f5cb3
Author: Pascal Schumacher 
AuthorDate: Fri Dec 20 15:22:11 2019 +0100

 FastjsonDataFormat: Use the build serializerFeatureList to configure
FastJson.
---
  .../java/org/apache/camel/component/fastjson/FastjsonDataFormat.java|
2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git
a/components/camel-fastjson/src/main/java/org/apache/camel/component/fastjson/FastjsonDataFormat.java
b/components/camel-fastjson/src/main/java/org/apache/camel/component/fastjson/FastjsonDataFormat.java
index ebff729..92de516 100644
---
a/components/camel-fastjson/src/main/java/org/apache/camel/component/fastjson/FastjsonDataFormat.java
+++
b/components/camel-fastjson/src/main/java/org/apache/camel/component/fastjson/FastjsonDataFormat.java
@@ -120,7 +120,7 @@ public class FastjsonDataFormat extends ServiceSupport
implements DataFormat, Da

  serializerFeatureList.add(SerializerFeature.WriteDateUseDateFormat);
  config.setDateFormat(this.dateFormatPattern);
  }
-
+
config.setSerializerFeatures(serializerFeatureList.toArray(SerializerFeature[]::new));
  }
  }

Re: Sending camel-kafka-connector and camel-website github notification mails to camel-commits instead of camel-dev?

[Pascal Schumacher]

Great! Thank you very much!

Am 09.12.2019 um 20:07 schrieb Andrea Cosentino:

I already created an infra issue for camel-kafka-connector. I'll do the
same for the camel-website.

Il lun 9 dic 2019, 20:04 Pascal Schumacher  ha
scritto:


Hello,

what about sending the camel-kafka-connector and camel-website github
notification mails to the camel-commits mailing list instead of to the
camel-dev mailing list?

This would make the behavior consistent for camel, camel-k,
camel-website and camel-kafka-connector.

What do you think?

Cheers,

Pascal


Am 09.12.2019 um 16:38 schrieb GitBox:

valdar edited a comment on issue #31: run integration test insided gihub

actions

URL:

https://github.com/apache/camel-kafka-connector/issues/31#issuecomment-563296282


 See if it is possible to have integrations tests running as github

actions, not as heach PR but once in a while (nightly? weekly?).


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Sending camel-kafka-connector and camel-website github notification mails to camel-commits instead of camel-dev?

[Pascal Schumacher]

Hello,

what about sending the camel-kafka-connector and camel-website github
notification mails to the camel-commits mailing list instead of to the
camel-dev mailing list?

This would make the behavior consistent for camel, camel-k,
camel-website and camel-kafka-connector.

What do you think?

Cheers,

Pascal


Am 09.12.2019 um 16:38 schrieb GitBox:

valdar edited a comment on issue #31: run integration test insided gihub actions
URL: 
https://github.com/apache/camel-kafka-connector/issues/31#issuecomment-563296282


See if it is possible to have integrations tests running as github actions, 
not as heach PR but once in a while (nightly? weekly?).


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Closing down to Apache Camel 3.0 GA

[Pascal Schumacher]

Having another circuitBreaker implementation available in Camel would be
great, as Hystrix is no longer in active development (see:
https://github.com/Netflix/Hystrix#hystrix-status). Maybe Hystrix should
even be deprecated.

Am 14.11.2019 um 17:08 schrieb Claus Ibsen:

Hi

I have created a ticket about making hystrix EIP neutral as
circuitBreaker() so we can plugin different implementations
https://issues.apache.org/jira/browse/CAMEL-14182

This would be great to get done for 3.0 GA. I will start on this tomorrow.

On Mon, Oct 28, 2019 at 3:39 PM Claus Ibsen  wrote:

Hi

So today we landed the Spring Boot 2.2 upgrade to master branch, so
that was a great goal when we needed before GA.

There are about 40 items with the 3.0.0 as fixed version in the
roadmap, but as some are somewhat old, then all of those are not all
required.

So lets try to focus on getting the codebase ready for GA sooner, such
as mid/end of november.


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

Re: Github Integration broken?

[Pascal Schumacher]

Seem like I am missing the "linking of accounts through
https://gitbox.apache.org/setup/; step mentioned in
https://blogs.apache.org/infra/entry/apache-and-github-a-friendly

Sorry for the noise,

Pascal

Am 06.11.2019 um 18:27 schrieb Andrea Cosentino:

Did you follow the gitbox integration workflow?

Il mer 6 nov 2019, 18:22 Pascal Schumacher  ha
scritto:


Yes, the commit are no longer in the gitbox repo.

I am pushing to gitbox because when I try to push to the camel repo on
github it tells me that I am not authorized. Even-though I am part of
"The Apache Foundation" organization on github. Pushing to other github
repos works fine. Not sure what I am missing.

As far as I know pushing to gitbox is supported (it was working a few
days ago and it is working now, commits are synchronized with github).

Am 06.11.2019 um 08:31 schrieb Andrea Cosentino:

It seems your commits have been lost Pascal. Not sure what happened. Can
you please use the Github git repo to push? Are you using the gitbox git
repo actually?

Il mar 5 nov 2019, 23:23 Andrea Cosentino  ha

scritto:

There are troubles on GitHub today.

You can check on GitHub status website.

It's not your fault :-)

Il mar 5 nov 2019, 23:19 Pascal Schumacher 

ha

scritto:


Hi,

guess something is broken (not sure if it was me), because when I

pushed

some commits (using git push") I got error messages .

https://gitbox.apache.org/repos/asf?p=camel.git;a=summary show the
commits, but https://github.com/apache/camel/commits/master does not
display the commits.

Github also has a commit by coheigea ("Adding secure processing for a
few TransformerFactory instances") which is missing on
https://gitbox.apache.org/repos/asf?p=camel.git;a=summary

Sorry if I inadvertently broke something.

-Pascal

Re: Github Integration broken?

[Pascal Schumacher]

Yes, the commit are no longer in the gitbox repo.

I am pushing to gitbox because when I try to push to the camel repo on
github it tells me that I am not authorized. Even-though I am part of 
"The Apache Foundation" organization on github. Pushing to other github
repos works fine. Not sure what I am missing.

As far as I know pushing to gitbox is supported (it was working a few
days ago and it is working now, commits are synchronized with github).

Am 06.11.2019 um 08:31 schrieb Andrea Cosentino:

It seems your commits have been lost Pascal. Not sure what happened. Can
you please use the Github git repo to push? Are you using the gitbox git
repo actually?

Il mar 5 nov 2019, 23:23 Andrea Cosentino  ha scritto:


There are troubles on GitHub today.

You can check on GitHub status website.

It's not your fault :-)

Il mar 5 nov 2019, 23:19 Pascal Schumacher  ha
scritto:


Hi,

guess something is broken (not sure if it was me), because when I pushed
some commits (using git push") I got error messages .

https://gitbox.apache.org/repos/asf?p=camel.git;a=summary show the
commits, but https://github.com/apache/camel/commits/master does not
display the commits.

Github also has a commit by coheigea ("Adding secure processing for a
few TransformerFactory instances") which is missing on
https://gitbox.apache.org/repos/asf?p=camel.git;a=summary

Sorry if I inadvertently broke something.

-Pascal

Github Integration broken?

[Pascal Schumacher]

Hi,

guess something is broken (not sure if it was me), because when I pushed
some commits (using git push") I got error messages .

https://gitbox.apache.org/repos/asf?p=camel.git;a=summary show the
commits, but https://github.com/apache/camel/commits/master does not
display the commits.

Github also has a commit by coheigea ("Adding secure processing for a
few TransformerFactory instances") which is missing on
https://gitbox.apache.org/repos/asf?p=camel.git;a=summary

Sorry if I inadvertently broke something.

-Pascal

Re: Notifications from camel-k & camel-quarkus github repos

[Pascal Schumacher]

Thank you very much!

Am 08.10.2019 um 08:32 schrieb Andrea Cosentino:

This should be resolved now.

Il giorno lun 7 ott 2019 alle ore 10:39 Nicola Ferraro 
ha scritto:


+1

I've so many filters in the mail that I didn't notice they were sent to
dev,
but definitely it's not the right place for commit notifications.

On Mon, Oct 7, 2019 at 10:23 AM Andrea Cosentino 
wrote:


Thanks for reporting this Tadayoshi, I didn't notice the flood on dev. I
thought it was already forwarded to commits.

Il giorno lun 7 ott 2019 alle ore 10:22 Tadayoshi Sato <
sato.tadayo...@gmail.com> ha scritto:


Thank you Andrea!

On Mon, Oct 7, 2019 at 4:15 PM Andrea Cosentino 

wrote:

https://issues.apache.org/jira/browse/INFRA-19233

Il giorno lun 7 ott 2019 alle ore 08:52 Willem Jiang <
willem.ji...@gmail.com>
ha scritto:


We could ask Apache Infra to forward the github notification to
commits or notification mailing list instead of flood the dev

mailing

list.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Oct 7, 2019 at 1:33 PM Tadayoshi Sato <

sato.tadayo...@gmail.com>

wrote:

Hi folks,

I've just realised that this dev mailing list is receiving a huge

amount

of

notifications from camel-k & camel-quarkus github repositories. I

am

a

bit

afraid that this overwhelms the actually discussions on camel

development

here and perhaps is making some who are willing to get involved

in

the

dev

discussions but not yet ready to be interested in camel-k &

camel-quarkus

developments scared of the mailing list and even be leaving.

For github activities I think those who are interested in the dev

of

camel-k & camel-quarkus are already 'watch'ing the repos so they

should

get

notified already, so it doesn't seem to make sense to route them

to

this

mailing list as well.

What do you think?  Is there any way to mitigate this?

Best regards,


--
Tadayoshi Sato

Re: [camel] 01/02: Remove the very outdated "Can I use Camel on Java 1.4" FAQ entry.

[Pascal Schumacher]

Sorry for breaking the navigation.

Thank you for fixing it!

- Pascal

Am 12.09.2019 um 13:06 schrieb Andrea Cosentino:

Hello, when we remove/modify a link or a name, don't forget to always run
the docs module in the camel project. It will check for dead xref.

In this case it was broken. I fixed it.

Il giorno gio 12 set 2019 alle ore 11:50  ha
scritto:


This is an automated email from the ASF dual-hosted git repository.

pascalschumacher pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git

commit d02e88989dcc30ccf4b5ae38e5db1735b65cb48e
Author: Pascal Schumacher 
AuthorDate: Thu Sep 12 11:45:09 2019 +0200

 Remove the very outdated "Can I use Camel on Java 1.4" FAQ entry.
---
  docs/user-manual/modules/ROOT/pages/faq.adoc | 1 -
  .../modules/ROOT/pages/faq/can-i-use-camel-on-java-14.adoc   | 9
-
  2 files changed, 10 deletions(-)

diff --git a/docs/user-manual/modules/ROOT/pages/faq.adoc
b/docs/user-manual/modules/ROOT/pages/faq.adoc
index 691e0c2..0e6a101 100644
--- a/docs/user-manual/modules/ROOT/pages/faq.adoc
+++ b/docs/user-manual/modules/ROOT/pages/faq.adoc
@@ -16,7 +16,6 @@ so please join in and help us make the documentation
better!
  General questions about Camel

  * xref:faq/can-i-get-commercial-support.adoc[Can I get commercial
support?]
-* xref:faq/can-i-use-camel-on-java-14.adoc[Can I use Camel on Java 1.4?]
  * xref:faq/does-camel-work-on-ibms-jdk.adoc[Does Camel work on IBM's JDK?]
  * xref:support.adoc[How can I get help?]
  * xref:faq/how-can-i-get-the-source-code.adoc[How can I get the source
code?]
diff --git
a/docs/user-manual/modules/ROOT/pages/faq/can-i-use-camel-on-java-14.adoc
b/docs/user-manual/modules/ROOT/pages/faq/can-i-use-camel-on-java-14.adoc
deleted file mode 100644
index 7dfe697..000
---
a/docs/user-manual/modules/ROOT/pages/faq/can-i-use-camel-on-java-14.adoc
+++ /dev/null
@@ -1,9 +0,0 @@
-[[CanIuseCamelonJava1.4-CanIuseCamelonJava1.4]]
-= Can I use Camel on Java 1.4?
-
-Apache Camel was developed to run on Java 1.5 or later to take advantage
-of the new language features like generics and annotations together with
-using the Java 5 concurrency code. Starting with version 2.7.0, only
-Java 1.6 is supported.
-
-Starting with version 2.10.0, Java 1.7 is supported, but not required.

Re: JUnit 5 support in camel

[Pascal Schumacher]

+1 to camel-test-junit5

Am 06.08.2019 um 17:10 schrieb Alex Dettinger:

Let me summarize the current options that have been evoked so far:
camel-test-jupiter
camel-test-junit-jupiter
camel-test-junit5
camel-test5

What do you think ?
Alex


On Tue, Aug 6, 2019 at 5:08 PM Alex Dettinger  wrote:


Hi guys,

   I've started the development of a new module adding the possibility to
write base camel-test with JUnit5. So far, I've named the module
camel-test-junit5, which would lead to a family of name like
camel-test-junit5-spring, camel-test-junit5-spring-boot...

   I would like to trigger a discussion around the naming of this module as
other candidate are also valid. For instance:
   camel-test-jupiter
  camel-test-junit-jupiter


https://github.com/apache/camel/pull/3084
https://issues.apache.org/jira/browse/CAMEL-13826

Re: [HEADS UP] - Mock endpoints now fail fast

[Pascal Schumacher]

+1

Am 02.08.2019 um 17:01 schrieb Claus Ibsen:

Hi

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

When you use assertIsSatisifed with mock endpoints during testing then
they will now fail fast if a message arrived that would cause an
expectation to fail, and there are still more messages expected.

Before the mock endpoint would only validate expectations when the
number of expected message had arrived.

This is default enabled and you can turn it off by setting
failFast=false on the mock endpoint in your routes - to use 2.x
behaviour. But I dont expect people to want to use this (but just in
case).

Re: [VOTE] Release Apache Camel 3.0.0-M1 (Milestone 1)

[Pascal Schumacher]

+1 (non-binding)

Tested by migrating flowable-camel to camel 3.0.0 
(https://github.com/flowable/flowable-engine/pull/1623).


The only think that was immediately obvious from the migration guide was 
that to stop routes you now use 
CamelContext.getRouteController().stopRoute(routeId) instead of 
CamelContext.stopRoute(routeId).


Thanks,
Pascal

Am 18.02.2019 um 08:22 schrieb Gregor Zurowski:

Hi Everyone:

This is a vote to release Apache Camel 3.0.0-M1, the first milestone
towards a new 3.0.0 major release with currently 366 improvements and
fixes.

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

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

Tarballs: 
https://repository.apache.org/content/repositories/orgapachecamel-1119/org/apache/camel/apache-camel/3.0.0-M1/

Tag: 
https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.0.0-M1

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

The vote is open for at least 72 hours.

Thanks,
Gregor

Re: Java 11 support

[Pascal Schumacher]

I'm also using 2.23 with Java 11 (components: spring-boot, servlet, 
http4, activemq, mail, smpp, scheduler...).


I had do add some dependencies for the removed JEE modules 
https://openjdk.java.net/jeps/320 (not sure if any were for Camel).


Am 07.01.2019 um 21:33 schrieb David Karlsen:

I am currently using 2.23 with java 11 just fine.

man. 7. jan. 2019 kl. 20:53 skrev Claus Ibsen :


Hi

Camel 3 will support Java 11.

We may do a "best-effort" support for a future Camel 2.x release,
maybe 2.24 or if we we end up doing a 2.25 release also.

On Mon, Jan 7, 2019 at 10:10 AM Rao Sanaka, Venkateswara
 wrote:

Hi,

Which version of Apache Camel does officially supports Java 11 platform?
Any probable timelines will be helpful.

Best Regards,
Venki.





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

onException onWhen behavior

[Pascal Schumacher]

Hi everybody,

I expected exceptionMessage() of onWhen() for a specific onException() 
to refer to the message of the exception instance in the exception 
hierarchy. E.g. I expected this to work:


public void configure() {
    onException(IOException.class)
    .onWhen(exceptionMessage().contains("root exception message"))
    .to("mock:ioexception");

    from("seda:start")
    .throwException(new RuntimeException("leaf exception message", 
new IOException("root exception message")));

}

Then I tried a custom predicate instead:

public void configure() {
    onException(IOException.class)
    .onWhen(method(IOExceptionMatcher.class))
    .to("mock:ioexception");

    from("seda:start")
    .throwException(new RuntimeException("leaf exception message", 
new IOException("root exception message")));

}

public static class IOExceptionMatcher {
    public static boolean matches(IOException e) {
    return e.getMessage().contains("root exception message");
    }
}

This also did not work. Therefore I tried:

public void configure() {
    onException(IOException.class)
    .onWhen(method(ExceptionMatcher.class))
    .to("mock:ioexception");

    from("seda:start")
    .throwException(new RuntimeException("leaf exception message", 
new IOException("root exception message")));

}

public static class ExceptionMatcher {
    public static boolean matches(Exception e) {
    return e.getMessage().contains("root exception message");
    }
}

This also did not work. This "workaround" does work:

public void configure() {
    onException(IOException.class)
    .onWhen(method(ExceptionMatcher.class))
    .to("mock:ioexception");

    from("seda:start")
    .throwException(new RuntimeException("leaf exception message", 
new IOException("root exception message")));

}

public static class ExceptionMatcher {
    public static boolean matches(Exception e) {
    return Throwables.getRootCause(e).getMessage().contains("root 
exception message");

    }
}

Is any of this supposed to work, or are my expectations wrong?

Thanks,
Pascal

Re: build camel-core JDK 11

[Pascal Schumacher]

No related to camel-core, but this commit 
https://github.com/apache/camel/commit/dda0e4c5890d8e12b5895b8736e3819d0b095d08 
can be reverted/dropped because groovy 2.5.3 should work on Java 11.


Am 06.11.2018 um 03:36 schrieb Onder SEZGIN:

Thanks Zoran. I can see you rebased already i ll try to give whole build a
go in a sandbox.

On Fri, Nov 2, 2018 at 4:16 PM Claus Ibsen  wrote:


On Fri, Nov 2, 2018 at 2:04 PM Zoran Regvart  wrote:

Hi Önder and Cameers,
I've just rebased and pushed additional changes on the `java-10-test`
branch. With this it should be possible to run:

`./mvnw -Pfastinstall clean install`

on Java 11.

since this is a milestone on getting Camel running on Java 11 I guess
I'm going to celebrate this a bit with an adult beverage...


I think Mr Camel would like that too. So I stashed some beers in the
fridge to celebrate in a few hours ;)


zoran

On Fri, Nov 2, 2018 at 9:42 AM, Zoran Regvart  wrote:

Hi Önder,
yeah I that would be it; I've not forgotten about this (read: still
rebasing), hopefully will get to the bottom of it today. I hit a snag
with Scala component, and it takes a long time for the build to run...

zoran

On Fri, Nov 2, 2018 at 8:22 AM, Onder SEZGIN 

wrote:

Hi Zoran,
it is ok now. apparently as i was not doing full build, i should have
installed parent/pom.xml otherwise camel-parent artifact from snapshot
repository was retrieved where the maven property was missing.
thanks.

On Thu, Nov 1, 2018 at 2:38 PM Onder SEZGIN 

wrote:

I think it should have been defined. it is in paren/pom.xml.
Not sure why it is not detected.

On Thu, Nov 1, 2018 at 12:08 PM Zoran Regvart 

wrote:

Hi Önder,
looks like the `annotation-api-version` Maven property is not

defined.

Is this on the `java-10-test` branch? I must have missed it when
rebasing on `master`, let me rebase and test locally now,

zoran

On Thu, Nov 1, 2018 at 3:19 AM, Onder SEZGIN 

wrote:

Hi,

Has anybody tried to build camel-core locally with JDK-11?

First i got this error;

[ERROR] Failed to execute goal


org.apache.camel:camel-package-maven-plugin:2.23.0-SNAPSHOT:prepare-spring-boot-auto-configuration

(validate) on project camel-core: Execution validate of goal


org.apache.camel:camel-package-maven-plugin:2.23.0-SNAPSHOT:prepare-spring-boot-auto-configuration

failed: A required class was missing while executing


org.apache.camel:camel-package-maven-plugin:2.23.0-SNAPSHOT:prepare-spring-boot-auto-configuration:

javax/xml/bind/annotation/XmlTransient

Then, i ran mvn clean install -Pfastinstall
inside tooling/maven/camel-package-maven-plugin.

Later while trying to build camel-core, i got another error.

[INFO] ---


camel-package-maven-plugin:2.23.0-SNAPSHOT:generate-components-list

(components) @ camel-core ---
[WARNING] The POM for


javax.annotation:javax.annotation-api:jar:${annotation-api-version} is

missing, no dependency information available
[DEBUG] Dependency collection stats:

{ConflictMarker.analyzeTime=155216,

ConflictMarker.markTime=138430, ConflictMarker.nodeCount=155,
ConflictIdSorter.graphTime=86832,

ConflictIdSorter.topsortTime=122681,

ConflictIdSorter.conflictIdCount=58,
ConflictIdSorter.conflictIdCycleCount=0,
ConflictResolver.totalTime=15833299,
ConflictResolver.conflictItemCount=107,
DefaultDependencyCollector.collectTime=343830160,
DefaultDependencyCollector.transformTime=16495156}
[DEBUG]

org.apache.camel:camel-package-maven-plugin:jar:2.23.0-SNAPSHOT:

[DEBUG]

org.apache.camel:json-simple-ordered:jar:2.23.0-SNAPSHOT:compile

[DEBUG]com.github.mvel:mvel:jar:97071e83fb:compile
[DEBUG]org.apache.maven:maven-core:jar:2.2.1:compile
[DEBUG]   org.apache.maven:maven-settings:jar:2.2.1:compile
[DEBUG]


org.apache.maven:maven-plugin-parameter-documenter:jar:2.2.1:compile

[DEBUG]
  org.apache.maven.reporting:maven-reporting-api:jar:2.2.1:compile
[DEBUG]

org.apache.maven.doxia:doxia-sink-api:jar:1.1:compile

[DEBUG]

org.apache.maven.doxia:doxia-logging-api:jar:1.1:compile

[DEBUG]   org.apache.maven:maven-profile:jar:2.2.1:compile
[DEBUG]   org.apache.maven:maven-model:jar:2.2.1:compile
[DEBUG]

  org.apache.maven:maven-repository-metadata:jar:2.2.1:compile

[DEBUG]

  org.apache.maven:maven-error-diagnostics:jar:2.2.1:compile

[DEBUG]   commons-cli:commons-cli:jar:1.2:compile
[DEBUG]


org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-4:compile

[DEBUG]

  org.apache.maven:maven-artifact-manager:jar:2.2.1:compile

[DEBUG]
backport-util-concurrent:backport-util-concurrent:jar:3.1:compile
[DEBUG]   org.apache.maven:maven-monitor:jar:2.2.1:compile
[DEBUG]   classworlds:classworlds:jar:1.1:compile
[DEBUG]

  org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3:compile

[DEBUG]  org.sonatype.plexus:plexus-cipher:jar:1.4:compile
[DEBUG]org.apache.maven:maven-artifact:jar:2.2.1:compile
[DEBUG]org.apache.maven:maven-plugin-api:jar:2.2.1:compile
[DEBUG]

org.apache.maven:maven-plugin-descriptor:jar:2.2.1:compile

[DEBUG]

Re: Apache Camel 2.21.3 Release

[Pascal Schumacher]

Am 02.10.2018 um 21:07 schrieb David Karlsen:

Maybe bump to boot 2.1 and spring 5.1 for 2.23?


+1, that would be great

Re: R: [camel] branch master updated: Revert "Upgrade TestContainers to version 1.9.0", because "org.testcontainers:testcontainers:jar:1.9.0" is not in maven central yet.

[Pascal Schumacher]

No problem, I just wanted to fix the build on builds.apache.org:

e.g.: 
https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/623/console


org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
on project camel-testcontainers:
Could not resolve dependencies for project 
org.apache.camel:camel-testcontainers:jar:2.23.0-SNAPSHOT:
Could not find artifact org.testcontainers:testcontainers:jar:1.9.0 in central 
(https://repo.maven.apache.org/maven2)

The testcontainer dependency is in maven central (see: 
https://search.maven.org/search?q=a:testcontainers) but version 1.9.0 is 
not there yet. Probably just some delay.


Cheers,
Pascal

Am 10.09.2018 um 23:17 schrieb Andrea Cosentino:

My fault. Probably it comes from a different repo. Sorry. I tested with 
camel-nats. I'll double check tomorrow
  
   Il lun, 10 set, 2018 alle 23:07, pascalschumac...@apache.org ha scritto:   This is an automated email from the ASF dual-hosted git repository.


pascalschumacher pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/master by this push:
     new ad8308c  Revert "Upgrade TestContainers to version 1.9.0", because 
"org.testcontainers:testcontainers:jar:1.9.0" is not in maven central yet.
ad8308c is described below

commit ad8308c3c942a51b6d346f17f6ddc57e5f1e6ed8
Author: Pascal Schumacher 
AuthorDate: Mon Sep 10 23:06:47 2018 +0200

     Revert "Upgrade TestContainers to version 1.9.0", because 
"org.testcontainers:testcontainers:jar:1.9.0" is not in maven central yet.
 
     This reverts commit 556a2935e38116258e4161ca29648636c118fb82.

---
  parent/pom.xml | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/parent/pom.xml b/parent/pom.xml
index 5f4115e..6d15f0c 100644
--- a/parent/pom.xml
+++ b/parent/pom.xml
@@ -680,7 +680,7 @@
     4.0.8
     1.2.1_1
     1.2.1
-    1.9.0
+    1.8.3
     6.14.2
     2.1.1
     1.18

   

Re: Java versions we wish to support

[Pascal Schumacher]

Am 19.07.2018 um 16:42 schrieb Zoran Regvart:

Hello,
while doing the exploration of running tests on Java 11 I found out
that from that version onward Java EE APIs are no longer distributed
with Java[1].

I think this makes a difference in how we declare the dependencies. So
for instance JAXB API is no longer available, we need to add it and we
have two options:

  1. declare in the  directly

If we declare it in the  directly, then some clients
might need to exclude that dependency: for instance application
servers might bundle a version of JAXB API and having another version
might lead to issues.

  2. declare in the  of the Java 11+ 

In this case Camel is OK when build/tested on Java 11+, but client
might get a ClassNotFoundException on Java 11+. This is based on my
understanding that Maven profiles in dependencies are considered only
at build time of the dependency, not when that dependency is used.

Am I wrong about this?


You are right.

I'm for declaring the dependencies directly. (This also means that Java 
9 / 10 users won't have to add the modules.)


As you said in case of a conflict users can exclude the dependencies.

Imho Camel should still support Java 8.

Regards,
Pascal

Re: [VOTE] Release Apache Camel 2.22.0

[Pascal Schumacher]

+1 (non-binding)

Tested with a spring-boot based project.

Thanks,
Pascal

Am 02.07.2018 um 14:38 schrieb Nicola Ferraro:

+1 (non-binding)

Tested on personal projects.

Thanks,
Nicola

On Mon, Jul 2, 2018 at 12:18 PM François Papon 
wrote:


+1 (non-binding)

Thanks,

François

Le 30 juin 2018 7:28 AM, Gregor Zurowski  a
écrit :

Hi Everyone:

This is a vote to release Apache Camel 2.22.0, a new minor release
with 216 new features, improvements and bug fixes. This release also
introduces support for Spring Boot 2.0. Please note that Spring Boot
1.x is no longer supported with this release. A summary of the changes
is available in the Camel wiki:
https://cwiki.apache.org/confluence/display/CAMEL/Camel+2.22.0+Release.

Release notes:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342707=12311211

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

Tarballs:

https://repository.apache.org/content/repositories/orgapachecamel-1107/org/apache/camel/apache-camel/2.22.0/

Tag:

https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.22.0

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

The vote is open for at least 72 hours.

Thanks,
Gregor

Re: 2.22.0 Release Notes - Incorrect Statement

[Pascal Schumacher]

Thanks!

Am 30.06.2018 um 14:58 schrieb Willem Jiang:

Done.
I removed the line.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sat, Jun 30, 2018 at 6:42 PM, Pascal Schumacher 
wrote:
Hi Willem,

currently I do not even have a confluence account, so it would be great if
you (or somebody else) could remove the line.

Thanks,
Pascal


Am 30.06.2018 um 12:27 schrieb Willem Jiang:


Hi Pascal,

Do you have right to update the wiki page?
If not, I can help you modify it, and you may ask Claus to give you the
edit right.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sat, Jun 30, 2018 at 4:33 PM, Pascal Schumacher <
pascalschumac...@gmx.net


wrote:
Hi,

this statement:

"The camel-jms Maven pom.xml file now exclude spring-messaging dependency
as this JAR is not used."

in the 2.22.0 release notes should be removed. This change was reverted
in:

https://github.com/apache/camel/commit/a93759079b667cd564da6
8a87adf22c48428f723

because of:

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

Thanks,

Pascal

Re: 2.22.0 Release Notes - Incorrect Statement

[Pascal Schumacher]

Hi Willem,

currently I do not even have a confluence account, so it would be great 
if you (or somebody else) could remove the line.


Thanks,
Pascal

Am 30.06.2018 um 12:27 schrieb Willem Jiang:

Hi Pascal,

Do you have right to update the wiki page?
If not, I can help you modify it, and you may ask Claus to give you the
edit right.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sat, Jun 30, 2018 at 4:33 PM, Pascal Schumacher 
wrote:
Hi,

this statement:

"The camel-jms Maven pom.xml file now exclude spring-messaging dependency
as this JAR is not used."

in the 2.22.0 release notes should be removed. This change was reverted in:

https://github.com/apache/camel/commit/a93759079b667cd564da6
8a87adf22c48428f723

because of:

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

Thanks,

Pascal

2.22.0 Release Notes - Incorrect Statement

[Pascal Schumacher]

Hi,

this statement:

"The camel-jms Maven pom.xml file now exclude spring-messaging 
dependency as this JAR is not used."


in the 2.22.0 release notes should be removed. This change was reverted in:

https://github.com/apache/camel/commit/a93759079b667cd564da68a87adf22c48428f723

because of:

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

Thanks,

Pascal

Re: Upgrade to Mina 2.0.19 broke camel-xmpp tests

[Pascal Schumacher]

Should have been "properly fix this".

Sorry,
Pascal

Am 19.06.2018 um 19:27 schrieb Pascal Schumacher:

Hi everybody,

after the recent updated to Mina 2.0.19 four camel-xmpp tests are broken:

https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/411/testReport/junit/org.apache.camel.component.xmpp/ 



I can replicated this locally. Reverting commit 
2b16d9b1c224e0d4b131f70017cf8010bb16edfe "Upgrade Mina to version 
2.0.19" makes the tests pass again.


No idea how to probably fix this, but I think we should fix this 
before releasing camel 2.22.


Cheers,

Pascal

Upgrade to Mina 2.0.19 broke camel-xmpp tests

[Pascal Schumacher]

Hi everybody,

after the recent updated to Mina 2.0.19 four camel-xmpp tests are broken:

https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/411/testReport/junit/org.apache.camel.component.xmpp/

I can replicated this locally. Reverting commit 
2b16d9b1c224e0d4b131f70017cf8010bb16edfe "Upgrade Mina to version 
2.0.19" makes the tests pass again.


No idea how to probably fix this, but I think we should fix this before 
releasing camel 2.22.


Cheers,

Pascal

Re: gRPC and Google Guava version

[Pascal Schumacher]

Am 18.06.2018 um 10:36 schrieb Claus Ibsen:

Hi

Guava has been a dependency nightmare and in earlier versions they
broke their APIs from time to time.

I recall seeing a statement from them a year or so ago, where they
acknowledge this and said they would
keep the APIs more stable so users can better use a specific version
of Guava on the classpath despite different frameworks
where set to use another versions.


Yes, I think they wait longer before deleting deprecated stuff nowadays, 
but they still break binary compatibility by deleting methods etc., e.g.:


https://github.com/google/guava/commit/ce6d93c20e143db79cc6b5c42109ca702e3acd55 

Re: [camel] branch master updated: Upgrade Commons DBCP2 to version 2.4.0

[Pascal Schumacher]

Hi Andrea,

this example seems to work (at least if I interpret the console output 
of "mvn camel:run" correctly.


Cheers,
Pascal

Am 17.06.2018 um 19:49 schrieb Andrea Cosentino:

If I remember correctly this should be break the camel-example-sql-blueprint, I 
have to verify.

--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Sunday, June 17, 2018, 7:02:55 PM GMT+2, pascalschumac...@apache.org 
 wrote:





This is an automated email from the ASF dual-hosted git repository.

pascalschumacher pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/master by this push:
     new 55bd2cc  Upgrade Commons DBCP2 to version 2.4.0
55bd2cc is described below

commit 55bd2ccc8457430836d9aa1192d6d635965933e1
Author: Pascal Schumacher 
AuthorDate: Sun Jun 17 14:33:07 2018 +0200

     Upgrade Commons DBCP2 to version 2.4.0
---
parent/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/parent/pom.xml b/parent/pom.xml
index ec0e53d..4537d98 100644
--- a/parent/pom.xml
+++ b/parent/pom.xml
@@ -145,7 +145,7 @@
     1.4
     1.0.15
     1.4
-    2.2.0
+    2.4.0
     1.8.1
     2.1
     1.3

Re: JUnit5, was: testcontainers

[Pascal Schumacher]

Thanks for the information!

Part of camel already uses this version 
(https://github.com/apache/camel/commit/1ddd931d5cf2faea41e2d7454a9f04ed3985) 
and Zoran is looking into updating the remaining parts in 
https://issues.apache.org/jira/browse/CAMEL-12586


Cheers,
Pascal

Am 17.06.2018 um 00:29 schrieb David Karlsen:

It is released now!

Den ons. 23. mai 2018 kl. 10:32 skrev Zoran Regvart :


Hi David,
yes we can wait for that and the Surefire/Failsafe release that
includes it. I think we can also add
org.junit.platform:junit-platform-surefire-provider:1.2.0 dependency
to the existing Surefire/Failsafe plugin configurations.

As far as I understand that issue is tracking the incorporation of the
existing codebase from JUnit5 into Surefire.

zoran

On Wed, May 23, 2018 at 10:15 AM, David Karlsen 
wrote:

Would you have to await for
https://issues.apache.org/jira/browse/SUREFIRE-1330 to be merged to get
surefire support?

Den ons. 23. mai 2018 kl. 10:08 skrev Zoran Regvart :


Hi,
on the testcontainers thread I mentioned that we can switch to JUnit5.
I've attended a talk by Sam Brannen at the local JUG. I think it was a
variant of the talk[1] he gave at SpringOne 2017.

The key takeaway for me was that JUnit5 is forward and backward
compatible, so you can run the same tests written with JUnit4
annotations on JUnit5, but you can also run JUnit5 tests on JUnit4, if
for some reason that would make sense in a particular case.

What I understood is that we could upgrade to JUnit5 by simply
upgrading the surefire/failsafe Maven plugins and adding the
junit-vintage-engine dependency but only to a module that has mixed
JUnit4 and JUnit5 tests[2]. The only issue is limited @Rule support.

Now on to the benefits, I think it makes much sense to move over to
JUnit5 for the conditional test execution[3], better categorization of
tests via tags[4] and the much better extension model[5].

I propose that we schedule this for the one release after the pending
one (so in 2.23), and that we add camel-test-jupiter component that
would help developers write nicer tests for their integrations with
support for dependency injection for example[6].

zoran

[1] https://www.youtube.com/watch?v=h0Idcz71Aog
[2]
https://junit.org/junit5/docs/current/user-guide/#migrating-from-junit4
[3]


https://junit.org/junit5/docs/current/user-guide/#writing-tests-conditional-execution

[4]


https://junit.org/junit5/docs/current/user-guide/#writing-tests-tagging-and-filtering

[5] https://junit.org/junit5/docs/current/user-guide/#extensions
[6]


https://junit.org/junit5/docs/current/user-guide/#writing-tests-dependency-injection

--
Zoran Regvart



--
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen



--
Zoran Regvart

Re: Daily build to test with JDK 9 and 10

[Pascal Schumacher]

Hi Zoran,

it is exactly as you said. Just parallelizing the test part of the build 
did not work for the reasons you mentioned. Therefore I have reverted 
the change.


- Pascal

Am 11.05.2018 um 00:05 schrieb Zoran Regvart:

Hi Pascal,
thank you for looking into this. I don't think that using parallel
will help us, here's why: we're building on JDK 8 and we need to use
binaries built on JDK 8. Running same tests in parallel will cause a
lot of flakiness as they might use the same network ports or touch the
same files. So that leaves us with copying the build workspace for
each JDK we want to additionally test before the parallel step -- and
that would be a lot of IO. That's why I mentioned a copy-on-write
filesystem. With something like that, and Luca mentioned using docker,
we could cheaply fork the file system to run the two stages in
parallel.

Hope that makes sense...

zoran

On Thu, May 10, 2018 at 4:10 PM, Pascal Schumacher
<pascalschumac...@gmx.net> wrote:

It is great to have a build for JDK 9 and 10!

(Next step is JDK 11, which is already available according to
https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
:))

Making the job executing the test for JDK 9 and JDK 10 in parallel was easy:

https://github.com/apache/camel/commit/1c26b28145553e8db45f5b5412903d16ef1f6948

The job is still running
(https://builds.apache.org/view/A-D/view/Camel/job/Camel.daily/17/flowGraphTable/),
but peeking into the logout I guess this easy solution will not work. Both
stages are executed on the same node and are therefore using the same file
system which causes problems/conflicts with e.g. Apache Derby.

- Pascal


Am 10.05.2018 um 00:15 schrieb Zoran Regvart:

Hi Cameleers,
so it's not that bad[1] 77 tests failed in total. I think we need to
play with opening up some modules a bit. I'm a bit sad that it takes 9
hours for the job to run, when we add JDK 11 I would expect it to take
13 hours, would be nice if there was a way to just run the tests in
parallel on multiple JDKs.

zoran

[1]
https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel.daily/lastCompletedBuild/testReport/

Re: Daily build to test with JDK 9 and 10

[Pascal Schumacher]

It is great to have a build for JDK 9 and 10!

(Next step is JDK 11, which is already available according to 
https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix 
:))


Making the job executing the test for JDK 9 and JDK 10 in parallel was easy:

https://github.com/apache/camel/commit/1c26b28145553e8db45f5b5412903d16ef1f6948

The job is still running 
(https://builds.apache.org/view/A-D/view/Camel/job/Camel.daily/17/flowGraphTable/), 
but peeking into the logout I guess this easy solution will not work. 
Both stages are executed on the same node and are therefore using the 
same file system which causes problems/conflicts with e.g. Apache Derby.


- Pascal

Am 10.05.2018 um 00:15 schrieb Zoran Regvart:

Hi Cameleers,
so it's not that bad[1] 77 tests failed in total. I think we need to
play with opening up some modules a bit. I'm a bit sad that it takes 9
hours for the job to run, when we add JDK 11 I would expect it to take
13 hours, would be nice if there was a way to just run the tests in
parallel on multiple JDKs.

zoran

[1] 
https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel.daily/lastCompletedBuild/testReport/

Re: Build fails since AS2 component was added (camel-example-ceylon breaks build)

[Pascal Schumacher]

Hi Zoran,

thank you very much for fixing this. :)

-Pascal

Am 09.05.2018 um 10:10 schrieb Zoran Regvart:

Hi Cameleers,
we managed to get the Ceylon example to compile without the JAR
artefact being attached to the Maven reactor, this was required by the
Ceylon Maven plugin's goal to import dependencies. You can take a look
at this commit[1] for the details of the workaround.

Now we have 21 tests that have failed, I'll try to take a look at some
of those, if anyone else has some time to take a look that would be
very welcome, ping me on IRC or Gitter so we don't overlap.

Thanks to everyone on this effort, I now it's a bit tedious and the
long iteration times slow you down

zoran

[1] 
https://gitbox.apache.org/repos/asf?p=camel.git;a=commitdiff;h=4851da7738ac9dede4cb7f823ccce85bf6a8d4e5

Re: Build fails since AS2 component was added (camel-example-ceylon breaks build)

[Pascal Schumacher]

The AS2 related failure is gone! :)

https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/284/console

Sadly the build remains broken due because of the recently added 
camel-example-ceylon:


[ERROR] Failed to execute goal 
org.ceylon-lang:ceylon-maven-plugin:1.3.3:import-dependency (dependency) 
on project camel-example-ceylon: Cannot import module 
maven:org.apache.camel.camel-core/2.22.0-SNAPSHOT: Jar file 
/home/jenkins/jenkins-slave/workspace/Camel_master-CIGY56HHEDNGVJBWJRRHBZ64GKNJTCSYDKOPJS46W5IZTMAS3I2Q/camel-core/target/classes 
is a directory (must be a file) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to 
execute goal org.ceylon-lang:ceylon-maven-plugin:1.3.3:import-dependency 
(dependency) on project camel-example-ceylon: Cannot import module 
maven:org.apache.camel.camel-core/2.22.0-SNAPSHOT


Despite numerous tries (and already some hacky commits) we haven't been 
able to fix this.


At this point I suggest we revert this addition.

Are there any objections?

-Pascal

Am 07.05.2018 um 19:27 schrieb Pascal Schumacher:

Hi Zoran,

great work and great explanation, thank you very much! :)

It now works for me locally.

-Pascal

Am 07.05.2018 um 11:52 schrieb Zoran Regvart:

Hi Cameleers,
I think I've found the core issue and committed a solution, we'll see
how the build goes.

The issue was that we were using  to reference a javadoc
dependency, whereas we should be using . I think when a
multi-module Maven build is run without the goal that produces the
artifact the  resolves the dependency as pointing to the
modules `target/classes` directory instead of the artifact that is
previously built, cached or available in a remote repository. This
changes if the artifact is already present in the Maven reactor, and
then it points to the artifact built in the target directory. And
again it changes if  is switched with  to resolve
from local repository or, I would assume, from remote repository.

I could see this when running `mvn -X install` and `mvn -X test` -
that would fail; in `components/camel-as2` directory. The first would
output:

[DEBUG] Adding project path
file:/.../components/camel-as2/camel-as2-api/target/camel-as2-api-2.22.0-SNAPSHOT-javadoc.jar 



And the second would output:

[DEBUG] Adding project path
file:/.../components/camel-as2/camel-as2-api/target/classes/

This changed when I changed the  to a  and now when
I run `mvn test` the javadoc dependency is picked up from my local
repository:

[DEBUG] Adding project path
file:/.../.m2/repository/org/apache/camel/camel-as2-api/2.22.0-SNAPSHOT/camel-as2-api-2.22.0-SNAPSHOT-javadoc.jar 



I've changed all components that had javadoc
to javadoc, I hope this helps :)

zoran

Re: Build fails since AS2 component was added

[Pascal Schumacher]

Hi Zoran,

great work and great explanation, thank you very much! :)

It now works for me locally.

-Pascal

Am 07.05.2018 um 11:52 schrieb Zoran Regvart:

Hi Cameleers,
I think I've found the core issue and committed a solution, we'll see
how the build goes.

The issue was that we were using  to reference a javadoc
dependency, whereas we should be using . I think when a
multi-module Maven build is run without the goal that produces the
artifact the  resolves the dependency as pointing to the
modules `target/classes` directory instead of the artifact that is
previously built, cached or available in a remote repository. This
changes if the artifact is already present in the Maven reactor, and
then it points to the artifact built in the target directory. And
again it changes if  is switched with  to resolve
from local repository or, I would assume, from remote repository.

I could see this when running `mvn -X install` and `mvn -X test` -
that would fail; in `components/camel-as2` directory. The first would
output:

[DEBUG] Adding project path
file:/.../components/camel-as2/camel-as2-api/target/camel-as2-api-2.22.0-SNAPSHOT-javadoc.jar

And the second would output:

[DEBUG] Adding project path
file:/.../components/camel-as2/camel-as2-api/target/classes/

This changed when I changed the  to a  and now when
I run `mvn test` the javadoc dependency is picked up from my local
repository:

[DEBUG] Adding project path
file:/.../.m2/repository/org/apache/camel/camel-as2-api/2.22.0-SNAPSHOT/camel-as2-api-2.22.0-SNAPSHOT-javadoc.jar

I've changed all components that had javadoc
to javadoc, I hope this helps :)

zoran

Re: Build fails since AS2 component was added

[Pascal Schumacher]

As the failure still occurs, I took a look and was able to replicate it 
locally.


It occurs if I execute |"mvn test|" (like jenkins does) and do not have 
|camel-as2-api-2.22.0-SNAPSHOT-javadoc.jar| in my local maven repository.


If I execute |"mvn install|" the build works.

For some reason the javadoc artifact is not downloaded from the camel 
snapshot repository.


What is confusing me, is that the build of |camel-box| does not display 
the same problem, even though is very similar.



Am 02.05.2018 um 09:18 schrieb Claus Ibsen:

Hi

Andrea found out that missing docs is a problem, so we can just add an
basic doc file in the src/main/docs folder to make the build work.

Andrea maybe you can do this?

On Sun, Apr 29, 2018 at 2:42 PM, Pascal Schumacher
<pascalschumac...@gmx.net> wrote:

Hello everybody,

since the camel-as2 component was added, all master builds on
builds.apache.org fail with:

[INFO] BUILD FAILURE
...
[ERROR] Failed to execute goal
org.apache.camel:camel-api-component-maven-plugin:2.22.0-SNAPSHOT:fromApis
(generate-test-component-classes) on project camel-as2:
Error generating source for
org.apache.camel.component.as2.api.AS2ClientManager:
No public non-static methods found, make sure Javadoc is available as
project test dependency -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal
org.apache.camel:camel-api-component-maven-plugin:2.22.0-SNAPSHOT:fromApis
(generate-test-component-classes) on project camel-as2:
Error generating source for
org.apache.camel.component.as2.api.AS2ClientManager: No public non-static
methods found, make sure Javadoc is available as project test dependency

See e.g.:
https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/256/console

I guess something was forgotten when adding the component? It would be great
if somebody could fix this.

Thanks,

Pascal

Re: freemarker-version and freemarker-bundle-version

[Pascal Schumacher]

Hi Willem,

thanks for the info. :)

I'm not an OSGi user, so I'm not qualified to comment on this.

Do you plan to (or maybe you already did) create a Freemarker issue for 
this?


-Pascal

Am 02.05.2018 um 04:30 schrieb Willem Jiang:

It's not a good practices to use the dynamic import *[1] to workaround the
package import issue, as we use the OSGi bundle as the old jar.
We may need to work with Freemarker to build a right OSGi bundle for it.

[1]https://github.com/apache/freemarker/blob/2.3-gae/osgi.bnd#L50


Willem Jiang

Blog: http://willemjiang.blogspot.com (English)
   http://jnn.iteye.com  (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem

On Tue, May 1, 2018 at 5:10 PM, Pascal Schumacher <pascalschumac...@gmx.net>
wrote:


Hi Zoran,

thanks for the feedback.

Implemented in: https://github.com/apache/came
l/commit/6217ba02eb8fab1bea2a7252aa00a1d659c0ea3e

- Pascal


Am 30.04.2018 um 19:53 schrieb Zoran Regvart:


Hi Pascal,
I think you're spot on, I think we should use the freemarker as is and
remove the service mix one,

zoran

On Sun, Apr 29, 2018 at 10:08 AM, Pascal Schumacher
<pascalschumac...@gmx.net> wrote:


Hi,

while looking into updating the freemarker version used by camel I
noticed
that we have both freemarker-version and freemarker-bundle-version.

It looks like freemarker already is a OSGI bundle nowadays:

https://github.com/apache/freemarker/blob/2.3-gae/build.xml#L412

https://github.com/apache/freemarker/blob/2.3-gae/osgi.bnd

Do we still need the freemarker service mix bundle?

Cheers,

Pascal

Re: freemarker-version and freemarker-bundle-version

[Pascal Schumacher]

Hi Zoran,

thanks for the feedback.

Implemented in: 
https://github.com/apache/camel/commit/6217ba02eb8fab1bea2a7252aa00a1d659c0ea3e


- Pascal

Am 30.04.2018 um 19:53 schrieb Zoran Regvart:

Hi Pascal,
I think you're spot on, I think we should use the freemarker as is and
remove the service mix one,

zoran

On Sun, Apr 29, 2018 at 10:08 AM, Pascal Schumacher
<pascalschumac...@gmx.net> wrote:

Hi,

while looking into updating the freemarker version used by camel I noticed
that we have both freemarker-version and freemarker-bundle-version.

It looks like freemarker already is a OSGI bundle nowadays:

https://github.com/apache/freemarker/blob/2.3-gae/build.xml#L412

https://github.com/apache/freemarker/blob/2.3-gae/osgi.bnd

Do we still need the freemarker service mix bundle?

Cheers,

Pascal

Re: Milo test cases disabled

[Pascal Schumacher]

Hi Zoran,

thanks for creating the INFRA issue and getting this fixed. :)

-Pascal

Am 30.04.2018 um 10:51 schrieb Zoran Regvart:

Hi Cameleers,
JDK upgrade fixed[1] this, thank you for looking after the tests :)

zoran

[1] 
https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/256/testReport/org.apache.camel.component.milo/MonitorItemMultiConnectionsCertTest/testMonitorItem1/

On Fri, Apr 27, 2018 at 11:17 AM, Zoran Regvart <zo...@regvart.com> wrote:

Hello Jens and Pascal,
thank you for debugging this I've created an INFRA issue[1] to upgrade
the JDK 8 to 8u162 or newer. I think we can wait a bit and see if this
is something that INFRA can do quickly. An alternative would be to not
use "JDK 1.8 (latest)" JDK but to use "JDK 1.8.0_144 (unlimited
security)" JDK. I think it doesn't make much sense to go backwards a
version, so I suggest that we wait couple of days before doing that.

zoran

[1] https://issues.apache.org/jira/browse/INFRA-16452

On Fri, Apr 27, 2018 at 8:34 AM, Jens Reimann <jreim...@redhat.com> wrote:

Thanks Pascal,

I did receive the full log off list. And I think I know what is going on. I
do get an "Illegal Key Size" Exception, which probably means that the JVM
on that machine doesn't allow to use strong keys.

I am not sure if you can install the [1] "Unlimited Strength Jurisdiction
Policy Files" in this machine. So probably that means I have to downgrade
the keys for the Apache CI setup.

Let me know what you think.

Cheers

Jens

[1]
http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html

On Tue, Apr 24, 2018 at 12:47 PM, Pascal Schumacher <
pascalschumac...@gmx.net> wrote:


Hi Jens,

thanks for lookin into this!

Here is the camel-milo part of the console output of the build:


[INFO] < org.apache.camel:camel-milo

-

[INFO] Building Camel :: Milo 2.22.0-SNAPSHOT
  [201/765]
[INFO] [ jar
]-
[INFO]
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven) @
camel-milo ---
[INFO]
[INFO] --- maven-bundle-plugin:3.5.0:cleanVersions (versions) @
camel-milo ---
[INFO]
[INFO] --- maven-remote-resources-plugin:1.5:process
(process-resource-bundles) @ camel-milo ---
[INFO]
[INFO] --- camel-package-maven-plugin:2.22.0-SNAPSHOT:prepare-components
(prepare) @ camel-milo ---
[INFO]
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @
camel-milo ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 5 resources
[INFO] Copying 3 resources
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory /home/jenkins/jenkins-slave/
workspace/Camel_master-CIGY56HHEDNGVJBWJRRHBZ64GKNJTC
SYDKOPJS46W5IZTMAS3I2Q/components/camel-milo/target/
generated/camel/dataformats
[INFO] skip non existing resourceDirectory /home/jenkins/jenkins-slave/
workspace/Camel_master-CIGY56HHEDNGVJBWJRRHBZ64GKNJTC
SYDKOPJS46W5IZTMAS3I2Q/components/camel-milo/target/
generated/camel/languages
[INFO]
[INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @
camel-milo ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 21 source files to /home/jenkins/jenkins-slave/
workspace/Camel_master-CIGY56HHEDNGVJBWJRRHBZ64GKNJTC
SYDKOPJS46W5IZTMAS3I2Q/components/camel-milo/target/classes
[INFO]
[INFO] --- maven-resources-plugin:3.0.2:testResources
(default-testResources) @ camel-milo ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 7 resources
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile)
@ camel-milo ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-surefire-plugin:2.21.0:test (default-test) @ camel-milo
---
[INFO] Surefire report directory: /home/jenkins/jenkins-slave/
workspace/Camel_master-CIGY56HHEDNGVJBWJRRHBZ64GKNJTC
SYDKOPJS46W5IZTMAS3I2Q/components/camel-milo/target/surefire-reports
[INFO]
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running org.apache.camel.component.milo.
MonitorItemMultiConnectionsCertTest
[ERROR] Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed:
115.399 s <<< FAILURE! - in org.apache.camel.component.milo.
MonitorItemMultiConnectionsCertTest
[ERROR] testMonitorItem1(org.apache.camel.component.milo.
MonitorItemMultiConnectionsCertTest)  Time elapsed: 41.293 s  <<< FAILURE!
java.lang.AssertionError: mock://test1 Received message count. Expected:
<1> but was: <0>
 at org.apache.camel.component.milo.MonitorItemMultiConnectionsCer
tTest.testMonitorItem1(MonitorItemMultiConnectionsCertTest.java:130)

[ERROR] testMonitorItem1(org.apache.camel.component.milo.
MonitorItemMultiConnectionsCertTest)  Time elapsed: 36.976 s  <<&l

Build fails since AS2 component was added

[Pascal Schumacher]

Hello everybody,

since the camel-as2 component was added, all master builds on 
builds.apache.org fail with:


[INFO] BUILD FAILURE
...
[ERROR] Failed to execute goal 
org.apache.camel:camel-api-component-maven-plugin:2.22.0-SNAPSHOT:fromApis 
(generate-test-component-classes) on project camel-as2:
Error generating source for org.apache.camel.component.as2.api.AS2ClientManager:
No public non-static methods found, make sure Javadoc is available as project test 
dependency -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.camel:camel-api-component-maven-plugin:2.22.0-SNAPSHOT:fromApis 
(generate-test-component-classes) on project camel-as2:
Error generating source for 
org.apache.camel.component.as2.api.AS2ClientManager: No public non-static 
methods found, make sure Javadoc is available as project test dependency

See e.g.: 
https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/256/console


I guess something was forgotten when adding the component? It would be 
great if somebody could fix this.


Thanks,

Pascal

freemarker-version and freemarker-bundle-version

[Pascal Schumacher]

Hi,

while looking into updating the freemarker version used by camel I 
noticed that we have both freemarker-version and freemarker-bundle-version.


It looks like freemarker already is a OSGI bundle nowadays:

https://github.com/apache/freemarker/blob/2.3-gae/build.xml#L412

https://github.com/apache/freemarker/blob/2.3-gae/osgi.bnd

Do we still need the freemarker service mix bundle?

Cheers,

Pascal

Re: Milo test cases disabled

[Pascal Schumacher]

/:?]
    at 
org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3878) 
[classes/:?]
    at 
org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3642) 
[classes/:?]
    at 
org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3494) 
[classes/:?]
    at 
org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:209) 
[classes/:?]
    at 
org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3253) 
[classes/:?]
    at 
org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249) 
[classes/:?]
    at 
org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3272) 
[classes/:?]
    at 
org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3249) 
[classes/:?]
    at 
org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
[classes/:?]
    at 
org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3165) 
[classes/:?]
    at 
org.apache.camel.test.junit4.CamelTestSupport.startCamelContext(CamelTestSupport.java:721) 
[classes/:?]
    at 
org.apache.camel.test.junit4.CamelTestSupport.doSetUp(CamelTestSupport.java:383) 
[classes/:?]
    at 
org.apache.camel.test.junit4.CamelTestSupport.setUp(CamelTestSupport.java:272) 
[classes/:?]
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
~[?:1.8.0_152]
    at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
~[?:1.8.0_152]
    at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
~[?:1.8.0_152]

    at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_152]
    at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) 
[junit-4.12.jar:4.12]
    at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) 
[junit-4.12.jar:4.12]
    at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) 
[junit-4.12.jar:4.12]
    at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) 
[junit-4.12.jar:4.12]
    at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) 
[junit-4.12.jar:4.12]
    at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) 
[junit-4.12.jar:4.12]
    at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) 
[junit-4.12.jar:4.12]
    at org.junit.rules.RunRules.evaluate(RunRules.java:20) 
[junit-4.12.jar:4.12]
    at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) 
[junit-4.12.jar:4.12]
    at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) 
[junit-4.12.jar:4.12]
    at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) 
[junit-4.12.jar:4.12]
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) 
[junit-4.12.jar:4.12]
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) 
[junit-4.12.jar:4.12]
    at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) 
[junit-4.12.jar:4.12]
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) 
[junit-4.12.jar:4.12]
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) 
[junit-4.12.jar:4.12]
    at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) 
[junit-4.12.jar:4.12]
    at org.junit.runners.ParentRunner.run(ParentRunner.java:363) 
[junit-4.12.jar:4.12]
    at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) 
[surefire-junit4-2.21.0.jar:2.21.0]
    at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273) 
[surefire-junit4-2.21.0.jar:2.21.0]
    at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) 
[surefire-junit4-2.21.0.jar:2.21.0]
    at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) 
[surefire-junit4-2.21.0.jar:2.21.0]
    at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:379) 
[surefire-booter-2.21.0.jar:2.21.0]
    at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:340) 
[surefire-booter-2.21.0.jar:2.21.0]
    at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) 
[surefire-booter-2.21.0.jar:2.21.0]
    at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:413) 
[surefire-booter-2.21.0.jar:2.21.0]

Caused by: java.nio.channels.ClosedChannelException

Cheers,
Pascal

Am 24.04.2018 um 12:47 schrieb Pascal Schumacher:

Hi Jens,

thanks for lookin into this!

Here is the camel-milo part of the console output of the build:


[INFO] < org.apache.camel:camel-milo >-
[INFO] Building Camel :: Milo 2.22.0-SNAPSHOT [201/765]
[INFO] ---

Aw: Re: Milo test cases disabled

[Pascal Schumacher]

o.converter.ConverterTest
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.987 s 
- in org.apache.camel.component.milo.converter.ConverterTest
[INFO] Running org.apache.camel.component.milo.server.ServerLocalTest
[INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.76 s - 
in org.apache.camel.component.milo.server.ServerLocalTest
[INFO] Running 
org.apache.camel.component.milo.server.ServerSetCertificateManagerTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.935 s 
- in org.apache.camel.component.milo.server.ServerSetCertificateManagerTest
[INFO] Running 
org.apache.camel.component.milo.server.ServerSetSecurityPoliciesTest
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.755 s 
- in org.apache.camel.component.milo.server.ServerSetSecurityPoliciesTest
[INFO] 
[INFO] Results:
[INFO] 
[ERROR] Failures: 
[ERROR] 
org.apache.camel.component.milo.MonitorItemMultiConnectionsCertTest.testMonitorItem1(org.apache.camel.component.milo.MonitorItemMultiConnectionsCertTest)
[ERROR]   Run 1: 
MonitorItemMultiConnectionsCertTest.testMonitorItem1:130->CamelTestSupport.assertMockEndpointsSatisfied:920
 mock://test1 Received message count. Expected: <1> but was: <0>
[ERROR]   Run 2: 
MonitorItemMultiConnectionsCertTest.testMonitorItem1:130->CamelTestSupport.assertMockEndpointsSatisfied:920
 mock://test1 Received message count. Expected: <1> but was: <0>
[ERROR]   Run 3: 
MonitorItemMultiConnectionsCertTest.testMonitorItem1:130->CamelTestSupport.assertMockEndpointsSatisfied:920
 mock://test1 Received message count. Expected: <1> but was: <0>
[INFO] 
[INFO] 
[ERROR] Tests run: 27, Failures: 1, Errors: 0, Skipped: 0

Taken from 
https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/245/consoleFull
 
I am not sure if there are further logs (if there are I do not have access 
rights).

Cheers,
Pascal


Gesendet: Dienstag, 24. April 2018 um 10:44 Uhr
Von: "Jens Reimann" <jreim...@redhat.com>
An: dev@camel.apache.org
Betreff: Re: Milo test cases disabled
Hi Pascal,

thanks for your help.

As I don't have access to the resources of the build job, would it be
possible for your to send me the log files of the test.

Thanks

Jens

On Mon, Apr 23, 2018 at 7:26 PM, Pascal Schumacher <pascalschumac...@gmx.net
> wrote:

> Hi Jens,
>
> I disabled the test because at the time it was the only camel test that
> always failed on builds.apache.org (with an assertion error).
>
> Sadly I could not replicate the failure locally.
>
> Currently there are no build results on builds.apache.org with the
> assertion enabled.
>
> I have just reverted the commit so you can check the tests results of the
> camel-milo component on https://builds.apache.org/view
> /C/view/Apache%20Camel/job/Camel/job/master/ in 6+ hours for details.
>
> Cheers,
> Pascal
>
>
> Am 23.04.2018 um 16:42 schrieb Jens Reimann:
>
>> Hi,
>>
>> I just saw that some of the Milo unit tests got disabled in a recent
>> commit:
>>
>> ->
>> https://github.com/apache/camel/commit/6cdfae2c1db963ab7cc07[https://github.com/apache/camel/commit/6cdfae2c1db963ab7cc07]
>> e43bec2c4495bc6914c
>>
>> The commit just says:
>>
>> camel-milo: Disable MonitorItemMultiConnectionsCertTest because it
>> always
>> fails on builds.apache.org
>>
>> I would like to fix this rather than to disable this. So any information
>> about that would be helpful to me.
>>
>> Cheers
>>
>> Jens
>>
>>
>


--
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
_

Red Hat GmbH, www.de.redhat.com[http://www.de.redhat.com],
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB
153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham,
Michael O'Neill

Re: Milo test cases disabled

[Pascal Schumacher]

Hi Jens,

I disabled the test because at the time it was the only camel test that 
always failed on builds.apache.org (with an assertion error).


Sadly I could not replicate the failure locally.

Currently there are no build results on builds.apache.org  with the 
assertion enabled.


I have just reverted the commit so you can check the tests results of 
the camel-milo component on 
https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/ 
in 6+ hours for details.


Cheers,
Pascal

Am 23.04.2018 um 16:42 schrieb Jens Reimann:

Hi,

I just saw that some of the Milo unit tests got disabled in a recent commit:

   ->
https://github.com/apache/camel/commit/6cdfae2c1db963ab7cc07e43bec2c4495bc6914c

The commit just says:

  camel-milo: Disable MonitorItemMultiConnectionsCertTest because it always
fails on builds.apache.org

I would like to fix this rather than to disable this. So any information
about that would be helpful to me.

Cheers

Jens

Re: Jenkins Pipeline Build Missing Deploy Phase?

[Pascal Schumacher]

Hi Zoran,

thanks for looking into this!

The last build was successful, but nothing was deployed.

I guess we are affected by "MDEPLOY-193: deployAtEnd does not deploy 
artifacts for multi-module project with build extensions" 
https://issues.apache.org/jira/browse/MDEPLOY-193 (or 
https://issues.apache.org/jira/browse/MDEPLOY-226 or 
https://issues.apache.org/jira/browse/MDEPLOY-201). :(


- Pascal

Am 19.03.2018 um 08:58 schrieb Zoran Regvart:

Hello,
no luck, the build failed on `bom-generator-maven-plugin` because no
Maven artefact was attached for that module in Maven reactor. I've
replaced the `install` goal in `Build` stage with `deploy` as at that
point the Maven reactor is populated.
Previously deploying to ASF Maven repository was done by Jenkins Maven
plugin which kept track of all produced artefacts so it can be
performed separately from the main Maven build. With pipeline that is
no longer possible.
I've added `deployAtEnd` flag so we deploy to the repository only if
the build passes. This doesn't mean that the -SNAPSHOT artefacts in
pass code checks or unit/integration tests, but that's how it used to
work with in the previous job constalation[1].

zoran

[1] https://builds.apache.org/view/C/view/Apache Camel/job/Camel.trunk.notest/

On Sun, Mar 18, 2018 at 9:23 PM, Zoran Regvart <zo...@regvart.com> wrote:

Hi Pascal,
good catch! The `Deploy` stage was using `install` phase whereas it
should invoke the maven-deploy-plugin (i.e. `deploy:deploy`). Let's
see if artifacts get deployed in pipeline build 140[1].

I've also configured 4h polling period, seems that master wasn't built
from 15th, I'm not 100% sure if this is an issue with gitpubsub[2] or
with the way the job is configured. From what I understand Jenkins
should be notified of any change to any ASF git repository.

zoran

[1] 
https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/140/
[2] https://www.apache.org/dev/gitpubsub.html

On Sun, Mar 18, 2018 at 12:42 PM, Pascal Schumacher
<pascalschumac...@gmx.net> wrote:

Hello,

Jenkins successfully build camel a few hours ago, but when I try to build
only camel-core locally I get:

[INFO] Building Camel :: Core 2.22.0-SNAPSHOT
[INFO] [ jar
]-
Downloading from apache.snapshots:
http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/maven-metadata.xml
Downloading from apache.snapshots:
http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/camel-package-maven-plugin-2.22.0-SNAPSHOT.pom
[WARNING] The POM for
org.apache.camel:camel-package-maven-plugin:jar:2.22.0-SNAPSHOT is missing,
no dependency information available
Downloading from apache.snapshots:
http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/camel-package-maven-plugin-2.22.0-SNAPSHOT.jar

[ERROR] Plugin org.apache.camel:camel-package-maven-plugin:2.22.0-SNAPSHOT
or one of its dependencies could not be resolved: Could not find artifact
org.apache.camel:camel-package-maven-plugin:jar:2.22.0-SNAPSHOT in
apache.snapshots (http://repository.apache.org/snapshots/) -> [Help 1]

https://repository.apache.org/content/groups/snapshots/org/apache/camel/apache-camel/
does not contains 2.22.0-SNAPSHOT and the build output of
https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/139/console
does not contain any maven-deploy-plugin output.

So I guess the Jenkins pipeline build is missing the deploy phase, or are
camel-snapshot supposed to be deployed my some other means?

Cheers,

Pascal





--
Zoran Regvart

Jenkins Pipeline Build Missing Deploy Phase?

[Pascal Schumacher]

Hello,

Jenkins successfully build camel a few hours ago, but when I try to 
build only camel-core locally I get:


[INFO] Building Camel :: Core 2.22.0-SNAPSHOT
[INFO] [ jar 
]-
Downloading from apache.snapshots: 
http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/maven-metadata.xml
Downloading from apache.snapshots: 
http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/camel-package-maven-plugin-2.22.0-SNAPSHOT.pom
[WARNING] The POM for 
org.apache.camel:camel-package-maven-plugin:jar:2.22.0-SNAPSHOT is 
missing, no dependency information available
Downloading from apache.snapshots: 
http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/camel-package-maven-plugin-2.22.0-SNAPSHOT.jar


[ERROR] Plugin 
org.apache.camel:camel-package-maven-plugin:2.22.0-SNAPSHOT or one of 
its dependencies could not be resolved: Could not find artifact 
org.apache.camel:camel-package-maven-plugin:jar:2.22.0-SNAPSHOT in 
apache.snapshots (http://repository.apache.org/snapshots/) -> [Help 1]


https://repository.apache.org/content/groups/snapshots/org/apache/camel/apache-camel/ 
does not contains 2.22.0-SNAPSHOT and the build output of 
https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/139/console 
does not contain any maven-deploy-plugin output.


So I guess the Jenkins pipeline build is missing the deploy phase, or 
are camel-snapshot supposed to be deployed my some other means?


Cheers,

Pascal

Re: Usage of SocketFactory#createSocket(String host, int port)

[Pascal Schumacher]

Thanks for the feedback Claus and Andrea!

I did not find anything in the javadoc concerning default timeouts etc.

As SocketFactory is an abstract class, the behavior of 
#createSocket(String host, int port) of course depends on the concrete 
implementation in use, but at least the default implementation of Oracle 
Java 8 Update 152 connects without using a timeout.


I created https://issues.apache.org/jira/browse/CAMEL-12358 and 
https://github.com/apache/camel/pull/2258 for this.


Cheers,
Pascal

Am 16.03.2018 um 07:18 schrieb Claus Ibsen:

Yeah that sounds reasonable, have you checked the javadoc of the jdk
operations? But in all regards I do think your suggestion seems
better. You are welcome to do a PR / commit / JIRA etc.

On Tue, Mar 13, 2018 at 8:33 PM, Pascal Schumacher
<pascalschumac...@gmx.net> wrote:

Hello everybody,

took a look at the camel-smpp source code and noticed that is using
javax.net.SocketFactory#createSocket(String host, int port) which "creates a
socket and connects it to the specified port number at the specified
address" according to the javadoc.

As Socket#setSoTimeout is called later on and Socket#connect(SocketAddress
endpoint, int timeout) exists, I guess the initial connection is created
without any timeout?

As blocking operations without timeouts should be avoided, should the code
be changed to:

socket = socketFactory.createSocket();
socket.connect(new InetSocketAddress(host, port), timeout);

or am I missing something?

Thanks,

Pascal

Re: [ANNOUNCEMENT] Apache Camel 2.21.0 Released

[Pascal Schumacher]

Hello Gregor,

thank you very much for serving as the release manager.

-Pascal

Am 15.03.2018 um 20:30 schrieb Gregor Zurowski:

The Camel community announces the immediate availability of Camel
2.21.0 minor release. This release contains 400 fixes and improvements
committed in the past few weeks.

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-2210-release.html
[3] 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341576=12311211

Usage of SocketFactory#createSocket(String host, int port)

[Pascal Schumacher]

Hello everybody,

took a look at the camel-smpp source code and noticed that is using 
javax.net.SocketFactory#createSocket(String host, int port) which 
"creates a socket and connects it to the specified port number at the 
specified address" according to the javadoc.


As Socket#setSoTimeout is called later on and 
Socket#connect(SocketAddress endpoint, int timeout) exists, I guess the 
initial connection is created without any timeout?


As blocking operations without timeouts should be avoided, should the 
code be changed to:


socket = socketFactory.createSocket();
socket.connect(new InetSocketAddress(host, port), timeout);

or am I missing something?

Thanks,

Pascal

Re: R: [camel] branch master updated: RuntimeConfiguration#isAllowUseOriginalMessage: improve javadoc

[Pascal Schumacher]

I thought the branch will be created out of the "camel-2.21.0" tag if 
the vote passes?


(If it fails I would have expected a branch to be created out of the tag 
and and critical bugfixes be cherry-picked to this branch.)


Also Claus commited e.g. "Updated leveldb".

Am 12.03.2018 um 21:13 schrieb Andrea Cosentino:

In my opinioni we should stop committing stuff until the branch 2.21.x has been 
created. Unless we are talking about bugs. Just my opinion.

Inviato da Yahoo Mail su Android
  
   Il lun, 12 mar, 2018 alle 20:18, pascalschumac...@apache.org<pascalschumac...@apache.org> ha scritto:   This is an automated email from the ASF dual-hosted git repository.


pascalschumacher pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/master by this push:
     new 0bd8839  RuntimeConfiguration#isAllowUseOriginalMessage: improve 
javadoc
0bd8839 is described below

commit 0bd88399377dbfe0909c002f4e1d364d363e8122
Author: Pascal Schumacher <pascalschumac...@gmx.net>
AuthorDate: Mon Mar 12 20:18:08 2018 +0100

     RuntimeConfiguration#isAllowUseOriginalMessage: improve javadoc
---
  camel-core/src/main/java/org/apache/camel/RuntimeConfiguration.java | 6 ++
  1 file changed, 2 insertions(+), 4 deletions(-)

diff --git 
a/camel-core/src/main/java/org/apache/camel/RuntimeConfiguration.java 
b/camel-core/src/main/java/org/apache/camel/RuntimeConfiguration.java
index d523488..991e8cc 100644
--- a/camel-core/src/main/java/org/apache/camel/RuntimeConfiguration.java
+++ b/camel-core/src/main/java/org/apache/camel/RuntimeConfiguration.java
@@ -191,10 +191,8 @@ public interface RuntimeConfiguration {
     void setAllowUseOriginalMessage(Boolean allowUseOriginalMessage);
  
     /**

-    * Sets whether to allow access to the original message from Camel's error 
handler,
-    * or from {@link org.apache.camel.spi.UnitOfWork#getOriginalInMessage()}.
-    * 
-    * Turning this off can optimize performance, as defensive copy of the 
original message is not needed.
+    * Gets whether access to the original message from Camel's error handler,
+    * or from {@link org.apache.camel.spi.UnitOfWork#getOriginalInMessage()} 
is allowed.
       *
       * @return the option
       */

Re: I need some help with Spring XSD generation

[Pascal Schumacher]

Current builds see to get much further. 
https://builds.apache.org/job/Camel/job/master/90/console is currently 
building the camel starter! Great work!


I guess we should disable concurrent builds to keep load on 
build.apache.org reasonable?


Cheers,
Pascal

Am 28.02.2018 um 12:04 schrieb Zoran Regvart:

Thanks Claus great work!

I'm looking at https://builds.apache.org/job/Camel/job/master/88/
hoping for a green build.

If this goes through we can cherry pick CAMEL-11930 and these commits
to 2.20.x branch,

zoran

On Wed, Feb 28, 2018 at 11:49 AM, Claus Ibsen  wrote:

Hi

Okay I have pushed the fixes to the master branch, and I can now do
these 2 maven commands on both camel-spring and camel-blueprint and it
works.
So does the usual commands with mvn clean install and whatnot.

On Wed, Feb 28, 2018 at 11:25 AM, Claus Ibsen  wrote:

Hi

Okay I got it working, you can now run

mvn -Dmaven.test.skip.exec=true clean install

And then later

mvn test

I logged a ticket
https://issues.apache.org/jira/browse/CAMEL-12303

Will push a fix shortly, but runs a bit more testing.

Notice that we likely have the same issue in camel-blueprint so will
look at that guy afterwards

On Wed, Feb 28, 2018 at 10:56 AM, Claus Ibsen  wrote:

Hi Zoran

I am taking a look, and currently trying to improve the eip-document
enricher to do the schema1 copy itself so we can avoid this ant-task
in the pom.xml

On Tue, Feb 27, 2018 at 6:23 PM, Zoran Regvart  wrote:

Hi Cameleers,
I've been testing and cherry-picking commits that help with the
pipeline build[1] from `jenkins-pipeline` branch to `master`.

I was hoping on having a pipeline that would fail as soon as possible
by executing in turn build, checks, tests; so we don't wait for the
whole build to finish to find out if compile, checkstyle or test
fails.

Right now I'm stuck on an issue with Spring XSD, that I thought I
would workaround by simple `if` in the embedded Ant[2]. This isn't
working out.

I was hoping that `mvn -Dmaven.test.skip.exec=true clean install`
followed by `mvn test` would work, but it fails. Can someone take a
look and help me out?

Of course simple solution would be to run `install` goal with tests
enabled -- I was hoping on avoiding that...

Thanks :)

zoran

[1] https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/
[2] 
https://github.com/apache/camel/commit/9fbfad95b12a02c94578641798128dfb75fa0b67
--
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: Getting ready for Apache Camel 2.21 release

[Pascal Schumacher]

Am 26.02.2018 um 14:04 schrieb David Karlsen:

It would be super-nice if camel could do a release supporting spring-boot
2.x quite close to boot 2.x releasing!


+1, that would be great.

The planned release date of spring boot 2.0 is tomorrow, so if the camel 
spring boot 2.0 branch is ready it could theoretically be possible to 
support spring boot 2.0 with camel 2.21.

Re: Test failures on build.apache.org with current master / version conflicts in libraries?

[Pascal Schumacher]

Thanks for fixing this!

Am 12.02.2018 um 08:05 schrieb Andrea Cosentino:

Fixed, we were missing an Rx java dependency

--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Sunday, February 11, 2018, 2:45:41 PM GMT+1, Pascal Schumacher 
<pascalschumac...@gmx.net> wrote:





Hello everybody,

there seem to be some version conflicts in the libraries used by current
master. On build.apache.org these tests always fail:

org.apache.camel.spring.cloud.netflix.CamelCloudNetflixServiceCallTest.testServiceCall:


java.lang.ClassNotFoundException: rx.Single

org.apache.camel.component.boon.BoonDataFormatTest.testMarshalAndUnmarshalPojoMap:

org.apache.camel.component.bean.MethodNotFoundException: Method with
name: name not found on bean: {name=Camel} of type:
org.boon.core.value.LazyValueMap

-Pascal

Test failures on build.apache.org with current master / version conflicts in libraries?

[Pascal Schumacher]

Hello everybody,

there seem to be some version conflicts in the libraries used by current 
master. On build.apache.org these tests always fail:


org.apache.camel.spring.cloud.netflix.CamelCloudNetflixServiceCallTest.testServiceCall: 



java.lang.ClassNotFoundException: rx.Single

org.apache.camel.component.boon.BoonDataFormatTest.testMarshalAndUnmarshalPojoMap:

org.apache.camel.component.bean.MethodNotFoundException: Method with 
name: name not found on bean: {name=Camel} of type: 
org.boon.core.value.LazyValueMap


-Pascal

Re: logback-version in parent pom

[Pascal Schumacher]

Am 05.02.2018 um 23:05 schrieb Pascal Schumacher:

Hi everybody,

the camel parent pom defines a logback-version property, but it does 
not seem to be used anywhere ("git grep logback-version" does not 
display any other results). Can this property be removed?


- Pascal


The same goes for the "log4j2-25-version" property.

logback-version in parent pom

[Pascal Schumacher]

Hi everybody,

the camel parent pom defines a logback-version property, but it does not 
seem to be used anywhere ("git grep logback-version" does not display 
any other results). Can this property be removed?


- Pascal

Re: org.apache.camel.component.ribbon.springboot.cloud.RibbonLoadBalancerTest.testLoadBalancer test failure

[Pascal Schumacher]

Am 14.01.2018 um 13:38 schrieb Claus Ibsen:

Yeah we should add that as test dependency as its used in the unit
test (http4 is the default component the service call eip uses).

Did not know that. Thanks!

So you are welcome to add that.

Just did.

Cheers,
Pascal

org.apache.camel.component.ribbon.springboot.cloud.RibbonLoadBalancerTest.testLoadBalancer test failure

[Pascal Schumacher]

Hello everyone,

org.apache.camel.component.ribbon.springboot.cloud.RibbonLoadBalancerTest.testLoadBalancer 
always fails on build.apache.org and locally with:


Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.342 
sec <<< FAILURE! - in 
org.apache.camel.component.ribbon.springboot.cloud.RibbonLoadBalancerTest
testLoadBalancer(org.apache.camel.component.ribbon.springboot.cloud.RibbonLoadBalancerTest) 
Time elapsed: 0.301 sec  <<< ERROR!
org.apache.camel.CamelExecutionException: Exception occurred during 
execution on the exchange: Exchange[ID--1515927432095-2-1]
    at 
org.apache.camel.component.ribbon.springboot.cloud.RibbonLoadBalancerTest.testLoadBalancer(RibbonLoadBalancerTest.java:72)
Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to 
resolve endpoint: http4://jetty:http://localhost:9091 due to: No 
component found with scheme: http4
    at 
org.apache.camel.component.ribbon.springboot.cloud.RibbonLoadBalancerTest.testLoadBalancer(RibbonLoadBalancerTest.java:72)


Adding camel-http4 as a test dependency fixes the failure, but I'm not 
sure it is the correct way to fix this.


-Pascal

Re: R: Re: R: Maven goal to generate component adoc?

[Pascal Schumacher]

Thanks! Maybe Windows is the cause.

Am 10.01.2018 um 20:25 schrieb Andrea Cosentino:

Weird, I'll take a look tomorrow :-)

Inviato da Yahoo Mail su Android
  
   Il mer, 10 gen, 2018 alle 20:20, Pascal Schumacher<pascalschumac...@gmx.net> ha scritto:   Thanks!


I tried that yesterday. First I made these changes:
https://github.com/apache/camel/commit/57d028fca3b35530cb98b39a2263431023b346c1
and than ran "mvn install" in the "camel\components\camel-ftp" directory.

Now I notice there an camel-apt-error.log file in the camel-ftp
directory containing:

Error processing @UriEndpoint

java.lang.NullPointerException
      at org.apache.camel.tools.apt.helper.IOHelper.close(IOHelper.java:73)
      at
org.apache.camel.tools.apt.DocumentationHelper.findEndpointJavaDoc(DocumentationHelper.java:74)
      at
org.apache.camel.tools.apt.EndpointAnnotationProcessor.createParameterJsonSchema(EndpointAnnotationProcessor.java:316)
      at
org.apache.camel.tools.apt.EndpointAnnotationProcessor.writeJSonSchemeDocumentation(EndpointAnnotationProcessor.java:155)
      at
org.apache.camel.tools.apt.EndpointAnnotationProcessor$1.call(EndpointAnnotationProcessor.java:128)
      at
org.apache.camel.tools.apt.EndpointAnnotationProcessor$1.call(EndpointAnnotationProcessor.java:125)
      at
org.apache.camel.tools.apt.AnnotationProcessorHelper.processFile(AnnotationProcessorHelper.java:348)
      at
org.apache.camel.tools.apt.EndpointAnnotationProcessor.processEndpointClass(EndpointAnnotationProcessor.java:132)
      at
org.apache.camel.tools.apt.EndpointAnnotationProcessor.process(EndpointAnnotationProcessor.java:88)
      at
com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:794)
      at
com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:705)
      at
com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1800(JavacProcessingEnvironment.java:91)
      at
com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1035)
      at
com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1176)
      at
com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1170)
      at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:856)
      at com.sun.tools.javac.main.Main.compile(Main.java:523)
      at com.sun.tools.javac.main.Main.compile(Main.java:381)
      at com.sun.tools.javac.main.Main.compile(Main.java:370)
      at com.sun.tools.javac.main.Main.compile(Main.java:361)
      at com.sun.tools.javac.Main.compile(Main.java:56)
      at com.sun.tools.javac.Main.main(Main.java:42)

I guess it is because the javadoc:javadoc goal is not executed when
running "mvn install".

So I tried to run "mvn clean javadoc:javadoc install", but that fails
with javadoc errors.


Am 10.01.2018 um 20:03 schrieb Andrea Cosentino:

The install goal on a componenti will update the .adoc if something changed

Inviato da Yahoo Mail su Android
   
     Il mer, 10 gen, 2018 alle 20:01, Pascal Schumacher<pascalschumac...@gmx.net> ha scritto:  Hello everybody,


which maven goal generates the component adoc from the javadoc?

Thanks,

Pascal

 

   

Re: R: Maven goal to generate component adoc?

[Pascal Schumacher]

Thanks!

I tried that yesterday. First I made these changes: 
https://github.com/apache/camel/commit/57d028fca3b35530cb98b39a2263431023b346c1 
and than ran "mvn install" in the "camel\components\camel-ftp" directory.


Now I notice there an camel-apt-error.log file in the camel-ftp 
directory containing:


Error processing @UriEndpoint

java.lang.NullPointerException
    at org.apache.camel.tools.apt.helper.IOHelper.close(IOHelper.java:73)
    at 
org.apache.camel.tools.apt.DocumentationHelper.findEndpointJavaDoc(DocumentationHelper.java:74)
    at 
org.apache.camel.tools.apt.EndpointAnnotationProcessor.createParameterJsonSchema(EndpointAnnotationProcessor.java:316)
    at 
org.apache.camel.tools.apt.EndpointAnnotationProcessor.writeJSonSchemeDocumentation(EndpointAnnotationProcessor.java:155)
    at 
org.apache.camel.tools.apt.EndpointAnnotationProcessor$1.call(EndpointAnnotationProcessor.java:128)
    at 
org.apache.camel.tools.apt.EndpointAnnotationProcessor$1.call(EndpointAnnotationProcessor.java:125)
    at 
org.apache.camel.tools.apt.AnnotationProcessorHelper.processFile(AnnotationProcessorHelper.java:348)
    at 
org.apache.camel.tools.apt.EndpointAnnotationProcessor.processEndpointClass(EndpointAnnotationProcessor.java:132)
    at 
org.apache.camel.tools.apt.EndpointAnnotationProcessor.process(EndpointAnnotationProcessor.java:88)
    at 
com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:794)
    at 
com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:705)
    at 
com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1800(JavacProcessingEnvironment.java:91)
    at 
com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1035)
    at 
com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1176)
    at 
com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1170)

    at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:856)
    at com.sun.tools.javac.main.Main.compile(Main.java:523)
    at com.sun.tools.javac.main.Main.compile(Main.java:381)
    at com.sun.tools.javac.main.Main.compile(Main.java:370)
    at com.sun.tools.javac.main.Main.compile(Main.java:361)
    at com.sun.tools.javac.Main.compile(Main.java:56)
    at com.sun.tools.javac.Main.main(Main.java:42)

I guess it is because the javadoc:javadoc goal is not executed when 
running "mvn install".


So I tried to run "mvn clean javadoc:javadoc install", but that fails 
with javadoc errors.



Am 10.01.2018 um 20:03 schrieb Andrea Cosentino:

The install goal on a componenti will update the .adoc if something changed

Inviato da Yahoo Mail su Android
  
   Il mer, 10 gen, 2018 alle 20:01, Pascal Schumacher<pascalschumac...@gmx.net> ha scritto:   Hello everybody,


which maven goal generates the component adoc from the javadoc?

Thanks,

Pascal

   

Maven goal to generate component adoc?

[Pascal Schumacher]

Hello everybody,

which maven goal generates the component adoc from the javadoc?

Thanks,

Pascal

Re: [DISCUSS] - Apache Camel 2.20.2 release

[Pascal Schumacher]

Happy new year everybody,

+1 a 2.20  bugfix release would be great (I am eagerly awaiting a 
release containing the bugfix for CAMEL-12069).


Cheers,
Pascal

Am 10.01.2018 um 14:02 schrieb Claus Ibsen:

Hi

Welcome to 2018.

I think we should get a new patch release of Camel 2.20.x out the door
in the foresable future. Maybe by the end of this month or so.

Gregor, do you have time to help cut a new release?

Camel - 2.20.x - Test failure: camel model - NoSuchMethodException: CastorDataFormat#getWhitelistEnabled

[Pascal Schumacher]

Hello everybody,

on build.apache.org there is one consistent failure (last 38 builds) for Camel 
2.20.x:

org.apache.camel.model.ModelSanityCheckerTest.testSanity

java.lang.NoSuchMethodException: 
org.apache.camel.model.dataformat.CastorDataFormat.getWhitelistEnabled()
at 
org.apache.camel.model.ModelSanityCheckerTest.testSanity(ModelSanityCheckerTest.java:83)

Any ideas how to fix this?

Cheers,
Pascal