unsubscribe
- Original Message -
From: "Gregor Zurowski"
To: dev@camel.apache.org, us...@camel.apache.org, annou...@apache.org
Sent: Wednesday, January 27, 2016 1:52:41 PM
Subject: [ANNOUNCEMENT] Apache Camel 2.16.2 Released
The Camel community announces the immediate availability
The Camel community announces the immediate availability of the new
patch release Camel 2.16.2. This release contains over 70 fixes
applied in the past few weeks by the community on the Camel 2.16.x
maintenance branch.
The artifacts are published and ready for you to download [1] either
from the A
GitHub user hqstevenson opened a pull request:
https://github.com/apache/camel/pull/813
CAMEL-9493 - Improve shutdown of listener for consumer
Also updated the tests so they all use "localhost" instead of "0.0.0.0"
You can merge this pull request into a Git repository by running:
GitHub user brreitme opened a pull request:
https://github.com/apache/camel/pull/812
CAMEL-8742 - Reconnect when connections are closed.
* Publishers and subscribers will reconnect if the connection / channel is
closed
* Cancel reply manager when sending a message in the produce
This vote passes with the following results:
+1 binding: 6 (Aki Yoshida, Andrea Cosentino, Christian Müller, Claus
Ibsen, Gregor Zurowski, Jon Anstey)
+1 non-binding: 2 (Grzegorz Grzybek, Thomas Diesler)
I'll promote the artifacts shortly.
Thanks,
Gregor
On Sat, Jan 23, 2016 at 12:08 PM, Grego
+1
Thanks,
Gregor
On Sat, Jan 23, 2016 at 12:08 PM, Gregor Zurowski
wrote:
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.16.2 that has 70+ fixes and
> improvements.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12334167
>
>
Sunil -
I asked about the property placeholders because there were a lot of issues with
CamelBlueprintTestSupport, property placeholders and synchronization. I think
these issues have been resolved in the later versions of Camel.
Is it possible to test the route using Camel 2.16.1 to see if yo
Github user lburgazzoli closed the pull request at:
https://github.com/apache/camel/pull/810
---
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 astefanutti closed the pull request at:
https://github.com/apache/camel/pull/811
---
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
On Wed, Jan 27, 2016 at 4:10 PM, Antonin Stefanutti
wrote:
> I’ve just tried it successfully for the Twitter component (both component and
> endpoint options).
>
> That’d be nice to have the ability to style the description. For example
> {@code TwitterComponent} from the Javadoc would render as
I’ve just tried it successfully for the Twitter component (both component and
endpoint options).
That’d be nice to have the ability to style the description. For example {@code
TwitterComponent} from the Javadoc would render as an inline code block in the
description column.
Antonin
> On 27
GitHub user astefanutti opened a pull request:
https://github.com/apache/camel/pull/811
Twitter component Asciidoc documentation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/astefanutti/camel twitter.adoc
Alternatively you ca
Hi
I just added support for component option as well, so its similar
style. Add comments but use component instead of endpoint.
And I enabled the goal to run on components/pom.xml so it runs by default now.
So you should be able to try this on all the existing .adoc files.
On Wed, Jan 27, 201
Ok, then we'll continue to import docs and when we have enough material we can
add comments everywhere :-)
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Wednesday, January
> On 27 Jan 2016, at 13:51, Claus Ibsen wrote:
>
> On Wed, Jan 27, 2016 at 1:07 PM, Antonin Stefanutti
> wrote:
>> Yes I think we should add the comments.
>>
>> For the SJMS and Metrics components, it shows the need to be able to
>> categorise the options. Obvious categories would be 'consume
On Wed, Jan 27, 2016 at 1:07 PM, Antonin Stefanutti
wrote:
> Yes I think we should add the comments.
>
> For the SJMS and Metrics components, it shows the need to be able to
> categorise the options. Obvious categories would be 'consumer' and 'producer'
> though for components like Metrics, some
On Wed, Jan 27, 2016 at 12:42 PM, Andrea Cosentino
wrote:
> Maybe we can start adding the comments
>
Yeah we could try that, basically move the plugin from camel-ahc to
the components/pom.xml so it runs for all those components.
It only do changes if there is an .adoc file and that it has those
Github user astefanutti closed the pull request at:
https://github.com/apache/camel/pull/809
---
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
Yes I think we should add the comments.
For the SJMS and Metrics components, it shows the need to be able to categorise
the options. Obvious categories would be 'consumer' and 'producer' though for
components like Metrics, some options are only applicable to a certain URI
remaining that are com
+1
Best,
Christian
On Sat, Jan 23, 2016 at 12:08 PM, Gregor Zurowski
wrote:
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.16.2 that has 70+ fixes and
> improvements.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12334167
>
Maybe we can start adding the comments
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Wednesday, January 27, 2016 11:25 AM, Claus Ibsen
wrote:
Hi
I worked a bit more on
Maybe we can start adding the comments
// endpoint options: START
// endpoint options: END
on the asciidoc we've already committed.
WDYT?
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github:
GitHub user lburgazzoli opened a pull request:
https://github.com/apache/camel/pull/810
CAMEL-6913 - Add dynamic unmarshalling capability to JiBX data format
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lburgazzoli/apache-came
Hi ,
Please add me to the mailing list of camel
Regards,
Kushagra.
0
down vote
favorite
1
I'm using camel beanio component to marshal and unmarshal the data inside
the file.
It is working fine in tomcat but not working in jboss. So I need to keep the
beanio mapping xml outside the war file. By mentioning actual path of
mapping xml file for mapping at
Hi
I worked a bit more on this and have made the plugin update the
existing adoc file (if present). And I have used the camel-ahc as
experiment.
The online page at
https://github.com/apache/camel/blob/master/components/camel-ahc/src/main/docs/ahc.adoc
Has all those endpoint options generated fro
GitHub user astefanutti opened a pull request:
https://github.com/apache/camel/pull/809
Asciidoc migration (Properties, Quickfix and RX components)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/astefanutti/camel asciidoc
Alter
Hi Claus,
Sure, I am closing this vote later today.
Thanks,
Gregor
On Wed, Jan 27, 2016 at 8:31 AM, Claus Ibsen wrote:
> Hi Gregor
>
> Wonder if you have time to close this vote and push the release out?
> So we can deliver the release to our community.
>
> On Sat, Jan 23, 2016 at 12:08 PM, Gr
Github user astefanutti closed the pull request at:
https://github.com/apache/camel/pull/808
---
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
29 matches
Mail list logo
