The Apache Jenkins build system has built Camel.2.17.x.notest (build #164)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.2.17.x.notest/164/
to view the results.
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1356
---
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 hqstevenson opened a pull request:
https://github.com/apache/camel/pull/1356
CAMEL-10511: Backport to 2.17
Updated MllpTcpClientProducer and MllpTcpServerConsumer to consume all
available data on socket
You can merge this pull request into a Git repository by running:
This is a vote to release Apache Camel 2.16.5, a new patch release that
includes a couple high importance fixes.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12338575&projectId=12311211
Staging repository:
https://repository.apache.org/content/repositorie
As long the artifactId is not change then its okay to move where the
source code is.
SB is so popular and having components-starter in the root highlights
that Camel has great SB support.
So its both good and bad.
On Fri, Dec 16, 2016 at 5:52 PM, Luca Burgazzoli wrote:
> Hello everyone,
>
> as
Hi
-0
We don't plan to remove deprecated code in 2.19.x.
But anything that is @deprecated will be removed for 3.0.
Also we have to be careful to not over admistrate ourselves. A while
back some people put every JAR upgrade in the wiki changelog which is
just too much burden. And if people wanted
Hello everyone,
as components-starter is platform specific (spring-boot), would it
make sense to move it to platforms/spring-boot ?
---
Luca Burgazzoli
Yes, absolutely :-)
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Friday, December 16, 2016 5:46 PM, Luca Burgazzoli
wrote:
Hello everyone,
wo
+1
Am 16.12.2016 um 17:46 schrieb Luca Burgazzoli:
Hello everyone,
would it make sense to open a JIRA to track the deprecated components
and code we want to remove for next camel release (2.19 or 3.0) ? So
people can know in advance what will be removed and we can easily list
them in the change
Hello everyone,
would it make sense to open a JIRA to track the deprecated components
and code we want to remove for next camel release (2.19 or 3.0) ? So
people can know in advance what will be removed and we can easily list
them in the change-log ?
---
Luca Burgazzoli
GitHub user johnpoth opened a pull request:
https://github.com/apache/camel/pull/1355
CAMEL-10608 Karaf endpoint-list command to support wildcard expressions
https://issues.apache.org/jira/browse/CAMEL-10608
You can merge this pull request into a Git repository by running:
$ gi
GitHub user zregvart opened a pull request:
https://github.com/apache/camel/pull/1354
CAMEL-9945 Upgrade to Jetty 9.3
In Jetty 9.3 API signature changed from:
List getProtocolHandler()
to:
ProtocolHandlers getProtocolHandler()
This commit adds reflection bridge t
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1352
---
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 asfgit closed the pull request at:
https://github.com/apache/camel/pull/1353
---
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
14 matches
Mail list logo
