I enabled the mail notification. It should go to comm...@camel.apache.org.
Could you please try whether it works? If not, I will ask INFRA for the
needed change...
Best,
Christian
On Wed, Jul 11, 2012 at 2:15 PM, Henryk Konsek wrote:
> Hi,
>
> It will be nice if commits to Camel Extra will be e
Yes, we will go with this version:
/**
http://code.google.com/a/apache-extras.org/p/camel-extra/
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Publ
The Apache Camel project [1] is a powerful open source integration
framework based on known Enterprise Integration Patterns [2].
The Camel community continues its efforts to issue patch releases on a
predictable schedule. Today we are proud to announce a new patch release
Apache Camel 2.8.6. This
Ah thanks for fixing it. BTW I googled a bit and it turned out to be a known
issue while using SVN:
http://stackoverflow.com/questions/767418/remove-unnecessary-svnmergeinfo-properties
Now just because of my curiosity, what change did you exactly commit into
the SVN to fix this issue? As I don't
Hi
Please use the @user mailing list for questions on using Camel and its
components.
There are many more people on that list to help and benefit from each other.
On Wed, Jul 11, 2012 at 1:04 PM, sarfaraj wrote:
> Hi,
>
> I am trying ssh component released in camel 2.10.0. It is working great.
Hi,
I am trying ssh component released in camel 2.10.0. It is working great.
However, I could not find any way to retrieve the return code of the script
that I am running. Similarly I could not find any way to get the errors
printed by the command on standard error.
Can someone help?
Thanks in
svn will update the svn mergeinfo property if it is there.
I already commit a fix to remove the mergeinfo property, it should be OK
now.
On 7/11/12 4:34 PM, Babak Vahdat wrote:
Hi
The same svn prop-change happened right before as well by Willem:
http://svn.apache.org/viewvc?view=revision&re
+1 for git support, have recently switched on all our internal projects,
really like Git.
--
View this message in context:
http://camel.465427.n5.nabble.com/DISCUSS-force-switching-from-SVN-to-GIT-tp5715773p5715860.html
Sent from the Camel Development mailing list archive at Nabble.com.
+1
--
View this message in context:
http://camel.465427.n5.nabble.com/DISCUSS-Camel-2-11-set-with-Spring-3-1-out-of-the-box-tp5715796p5715859.html
Sent from the Camel Development mailing list archive at Nabble.com.
Hi guys,
> Without a copyright statement, the date range is kind of pointless and just
> something else to keep updating. I'd pull that as well.
So can we stick to the version below?
BTW If we accept the license today (or tomorrow at most) I could fix
Camel Extra sources before I leave to my w
On Wednesday, July 11, 2012 12:31:35 AM Christian Müller wrote:
> Hello Henryk, hello Dan,
>
> @Henryk: Thanks for your work!
>
> @Dan: I will go forward with this tomorrow (or may be Henryk if he find
> some time) and change this line from the license header. Than I would
> suggest to use the fo
And of course such changes get propagated to the 2.9.x branch as well:
http://svn.apache.org/viewvc?view=revision&revision=1360057
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/Strange-SVN-Props-being-changed-by-each-commit-on-the-2-10-x-branch-tp5715762p5715847.html
Hi
The same svn prop-change happened right before as well by Willem:
http://svn.apache.org/viewvc?view=revision&revision=1360041
Note the change by this commit for the path:
camel/branches/camel-2.10.x/components/camel-http/
Interestingly it did *not* happen by the Claus's commit on last Monday
13 matches
Mail list logo
