The Apache Jenkins build system has built Camel.trunk.notest (build #3379)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3379/
to view the results.
The Apache Jenkins build system has built Camel.trunk.notest (build #3378)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3378/
to view the results.
Hi Cameleers,
+1
I'm all for releasing sooner, one blocker that I see with this is that
we can't really rely on the CI builds, they often break with out of
memory or artifact errors, perhaps we should also take the opportunity
to see if not using Jenkins Maven job type (for example Jenkins
pipeli
The Apache Jenkins build system has built Camel.trunk.notest (build #3377)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3377/
to view the results.
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1808
---
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 enab
GitHub user PascalSchumacher opened a pull request:
https://github.com/apache/camel/pull/1808
replace System.getProperty("line.separator") with System.lineSeparator()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/PascalSchumach
Hi
I think it can benefit the community if we try to get a 2.20 release
out after the summer break, such as in early/mid September.
The reason is that this release has some internal optimisations,
reduced object allocations, and faster startup that would benefit
Camel end users. Also end users ca
