The Apache Jenkins build system has built Camel.trunk.notest (build #3175)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3175/
to view the results.
Github user manosbatsis closed the pull request at:
https://github.com/apache/camel/pull/1659
---
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
Github user dmvolod closed the pull request at:
https://github.com/apache/camel/pull/1667
---
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 dmvolod opened a pull request:
https://github.com/apache/camel/pull/1667
CAMEL-11213: camel-grpc doesn't terminate channel when producer stops
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dmvolod/camel CAMEL-11213
+1 (personal projects)
On Thu, 27 Apr 2017 at 14:11, Claus Ibsen wrote:
> On Thu, Apr 27, 2017 at 12:03 PM, Gregor Zurowski
> wrote:
> > I can start creating the new release candidate on Saturday, if that
> > works for everyone.
> >
>
> +1
>
> That is a good time, then people have today and tom
Github user objectiser closed the pull request at:
https://github.com/apache/camel/pull/1664
---
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
Github user jamesnetherton closed the pull request at:
https://github.com/apache/camel/pull/1665
---
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
https://dentrassi.de/2017/04/27/opc-ua-with-apache-camel/
On Thu, Apr 27, 2017 at 1:03 PM, Tadayoshi Sato
wrote:
> Hi,
>
> I'll write an article summarising the 2.19 features/highlights in Japanese
> at qiita.com. qiita.com is the hottest knowledge sharing service for
> techies in Japan.
>
> On
GitHub user zregvart opened a pull request:
https://github.com/apache/camel/pull/1666
CAMEL-11212 Don't allow Salesforce HTTP client to stop with outstanding
requests
Submitted for review, it seems trivial but could have repercussions if I
missed the locking semantics.
Thank yo
GitHub user jamesnetherton opened a pull request:
https://github.com/apache/camel/pull/1665
CAMEL-10985: Ignore CORS configuraion in CoAP component
https://issues.apache.org/jira/browse/CAMEL-10985
You can merge this pull request into a Git repository by running:
$ git pull htt
GitHub user objectiser opened a pull request:
https://github.com/apache/camel/pull/1664
CAMEL-11211 Remove the deprecated SpanManager, which uses threadlocalâ¦
â¦, and instead just manage the spans within the exchanges
You can merge this pull request into a Git repository by runni
Hi
Can you log a JIRA, we need to take a look at that shutdown so the
thread pools are stopped after its done its work.
On Wed, Apr 26, 2017 at 6:18 PM, blove319 wrote:
> Camel versions tested: 2.16 - 2.18.3
> Current Maven dependencies:
> org.apache.camel:camel-test 2.18.1
> org.apache.camel:ca
On Thu, Apr 27, 2017 at 12:03 PM, Gregor Zurowski
wrote:
> I can start creating the new release candidate on Saturday, if that
> works for everyone.
>
+1
That is a good time, then people have today and tomorrow to get last
things into the master branch.
And as always please help test the curren
Hi,
I'll write an article summarising the 2.19 features/highlights in Japanese
at qiita.com. qiita.com is the hottest knowledge sharing service for
techies in Japan.
On Wed, Apr 26, 2017 at 4:36 PM, Claus Ibsen wrote:
> Hi Jens
>
> Yes this sounds good. You can post on your personal blog.
> And
Github user onders86 closed the pull request at:
https://github.com/apache/camel/pull/1663
---
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 can start creating the new release candidate on Saturday, if that
works for everyone.
Gregor
On Thu, Apr 27, 2017 at 11:46 AM, Claus Ibsen wrote:
> On Thu, Apr 27, 2017 at 10:58 AM, Gregor Zurowski
> wrote:
>> Hi Claus,
>>
>> Not a problem - I can take care of creating a new release candidate
On Thu, Apr 27, 2017 at 11:46 AM, Claus Ibsen wrote:
> Any thoughts from the +1 voters whom may be okay with a delay due to a
> new RC needs to be cut?
OK with me, I'm looking at a new Salesforce-Ping check issue that can
be included also
do we want to time box the re-cutting?
zoran
--
Zoran R
+1, it's better to have these commit in the new release
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Thursday, April 27, 2017 11:47 AM, Claus
On Thu, Apr 27, 2017 at 10:58 AM, Gregor Zurowski
wrote:
> Hi Claus,
>
> Not a problem - I can take care of creating a new release candidate,
> if we decide that we have too many issues with the current one.
>
Thanks that is good to know.
There has been a fair amount of commits since the RC (say
Github user zregvart closed the pull request at:
https://github.com/apache/camel/pull/1661
---
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
Hi Claus,
Not a problem - I can take care of creating a new release candidate,
if we decide that we have too many issues with the current one.
Thanks,
Gregor
On Thu, Apr 27, 2017 at 10:06 AM, Claus Ibsen wrote:
> I gave the RC a test with the source code for Camel in Action 2nd ed
> and it all
I gave the RC a test with the source code for Camel in Action 2nd ed
and it all passed.
There was a known issue with pax-exam which should not be related to
this RC but I would need to re-check to be really sure.
On the flip side we do have found a few issues and also the JPA bug
that was fixed i
22 matches
Mail list logo
