The Apache Jenkins build system has built Camel.2.19.x.notest (build #109)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.2.19.x.notest/109/
to view the results.
The Apache Jenkins build system has built Camel.2.19.x.notest (build #108)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.2.19.x.notest/108/
to view the results.
The Apache Jenkins build system has built Camel.trunk.notest (build #3443)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3443/
to view the results.
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1848
---
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
The Apache Jenkins build system has built Camel.2.19.x.notest (build #107)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.2.19.x.notest/107/
to view the results.
The Apache Jenkins build system has built Camel.trunk.notest (build #3442)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3442/
to view the results.
GitHub user pchhabra11 opened a pull request:
https://github.com/apache/camel/pull/1848
CAMEL-11586: added default camel route path
Possible Fix for https://issues.apache.org/jira/browse/CAMEL-11586.
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user onders86 opened a pull request:
https://github.com/apache/camel/pull/1847
CAMEL-5356 - handle if the value is an empty collection
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/onders86/camel CAMEL-5356
Alternativel
Github user johnpoth closed the pull request at:
https://github.com/apache/camel/pull/1846
---
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 en
I definitely agree, this is also a -1 for me. Glad that we caught it
early on. I will cut a new RC later today.
Thanks everyone for your participation so far.
Gregor
On Tue, Jul 25, 2017 at 2:06 PM, Zoran Regvart wrote:
> Hi Cameleers,
> I agree this would be quite unexpected for the users,
GitHub user johnpoth opened a pull request:
https://github.com/apache/camel/pull/1846
[CAMEL-11592] Exchange#addOnCompletion should route even if original â¦
â¦exchange has route stop / exception handled
https://issues.apache.org/jira/browse/CAMEL-11592
It might be bet
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1842
---
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
Hi Cameleers,
I agree this would be quite unexpected for the users, changing my vote to -1
zoran
On Tue, Jul 25, 2017 at 1:57 PM, Claus Ibsen wrote:
> Hi
>
> I have now pushed a fix to 2.19.x and master branch for that servlet
> dependency problem.
>
> I also tested that with the camel in actio
Hi
I have now pushed a fix to 2.19.x and master branch for that servlet
dependency problem.
I also tested that with the camel in action 2 source code which also
triggered this issue and failed an unit test/example.
Now it works again.
In light of this problem with this RC and that we have a fix
+1 for a new cut.
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Tuesday, July 25, 2017, 12:38:56 PM GMT+2, Claus Ibsen
wrote:
On Tue, Jul 25
On Tue, Jul 25, 2017 at 12:34 PM, Andrea Cosentino
wrote:
> Do we need to cut a new release?
>
Frankly I would prefer that as otherwise an upgrade is not as simple
as changing 2.19.1 to 2.19.2 for end users.
The HTTP components are commonly used components in Camel, its not a
little component th
Do we need to cut a new release?
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Tuesday, July 25, 2017, 12:06:51 PM GMT+2, Claus Ibsen
wrote:
On Tue, Jul 25, 2017 at 11:37 AM, Gary Brown wrote:
> Found the following issue: https://issues.apache.org/jira/browse/CAMEL-11591
>
Yeah same problem for camel-restlet which I just pushed a fix for.
We need to add that servlet api for the various http component that
uses it, jetty, http, http4,
Found the following issue: https://issues.apache.org/jira/browse/CAMEL-11591
This is a change from 2.19.1 to 2.19.2.
Regards
Gary
On Tue, Jul 25, 2017 at 9:40 AM, Zoran Regvart wrote:
> +1 (binding)
>
> Tested with Salesforce/Slack example and run the Salesforce integration
> tests,
>
> zoran
Github user dmvolod closed the pull request at:
https://github.com/apache/camel/pull/1843
---
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 ena
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1837
---
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
+1 (binding)
Tested with Salesforce/Slack example and run the Salesforce integration tests,
zoran
On Mon, Jul 24, 2017 at 10:15 PM, Gregor Zurowski
wrote:
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.19.2, a new patch release
> that includes 41 fixes and improvements.
>
> Release
22 matches
Mail list logo
