Hi,
I opened nabble and the archive in order to see if my message went through.
It was the case but the attachment was removed. So you can find the patch
right here: http://pastebin.com/WXtqUPGp
Have a nice day,
Antoine.
2013/2/4 Antoine DESSAIGNE
> Hi everyone,
>
> We use Camel 2.10.3 in or
For some reason still not clear to me, my mail client didn't get the
original thread started by Claus. That points to consensus that it's
time for a 2.10.4. I started a full build overnight and I am planning to
build the 2.10.4 release later this week, Wed or Thu.
Regarding 2.9.x, we did decid
When we do the release, the project version doesn't has the SNAPSHOT words.
I doubt the change will cause some trouble when we do the actual release.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjian
Github user grahamlittle closed the pull request at:
https://github.com/apache/camel/pull/5
A friendly reminder for our weekly IRC chat at irc://irc.codehaus.org/camel.
..
I will share the IRC log afterwards for who which could not attend.
Best,
Christian
--
Perhaps this is an opportunity for improvement. If anyone does any logo work,
why not just check the Gimp files into SVN to that other folks can use it too?
On Feb 2, 2013, at 11:27 AM, Christian Müller
wrote:
> I couldn't find anything in Camel or ActiveMQ SVN or the Confluence WIKI.
>
>
Rob, I totally agree with that.
Hadrian
On 02/04/2013 06:03 AM, Robert Davies wrote:
It is *NOT* OK to make defamatory comments about an organisation,
individuals or groups of people and use rumour and innuendo to do so.
On 1 February 2013 15:31, Hadrian Zbarcea wrote:
Rob, just drop it. Yo
It is *NOT* OK to make defamatory comments about an organisation,
individuals or groups of people and use rumour and innuendo to do so.
On 1 February 2013 15:31, Hadrian Zbarcea wrote:
> Rob, just drop it. You know very well James is right. A similar complaint
> was made just a few days ago abou
Hi
I think you should make it possible to configure this once on
JmsConfiguration / JmsComponent, Then you dont need to configure this
per endpoint.
Though if you configure per endpoint then it overrides the
configuration inherited from component.
Also the option could be exposed as a read-only J