GitHub user onders86 opened a pull request:
https://github.com/apache/camel/pull/1806
CAMEL-11516 - fix test with system.property("line.separator")
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/onders86/camel CAMEL-11516
Alter
Hi Zoran
Thanks for the heads-up. We no longer support JDK7 so that is good
timing. The Camel 2.18.x release requires JDK8.
On Wed, Jul 5, 2017 at 1:31 PM, Zoran Regvart wrote:
> Hi Cameleers,
> just as a hint if we want to build 2.17.x on builds.apache.org, the
> planned Jenkins upgrade next Sa
The Apache Jenkins build system has built Camel.2.18.x.notest (build #155)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.2.18.x.notest/155/
to view the results.
GitHub user onders86 opened a pull request:
https://github.com/apache/camel/pull/1805
CAMEL-11509 - check for semicolon added to call ContentType.create
As mentioned in the issue when ContentType.create is called for such cases,
it breaks HttpProducerContentTypeTest.java.
if not
Hi Cameleers,
just as a hint if we want to build 2.17.x on builds.apache.org, the
planned Jenkins upgrade next Saturday will make those incompatible as
Jenkins will not support running Maven jobs on JDK 7.
See discussion on buillds mailing list[1].
zoran
[1]
https://mail-archives.apache.org/mod
Github user aldettinger closed the pull request at:
https://github.com/apache/camel/pull/1804
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
The Apache Jenkins build system has built Camel.2.19.x.notest (build #80)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.2.19.x.notest/80/
to view the results.
Hi
I just pushed some commits that improves a little bit the startup of
Apache Camel. The Caffeine LRUCache will upon initialization block for
150 - 200 millis, which we can do in parallel while Camel is being
started. Before this initialization was always forced when you created
a new instance of
