GitHub user tivv opened a pull request:
https://github.com/apache/camel/pull/10
CAMEL-6057: Fix for accessing beans from parent context by type
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tivv/camel trunk
Alternatively you c
The redis component documentation is done, including a blog post about it
http://www.ofbizian.com/2013/02/apache-camel-meets-redis.html
Cheers
Bilgin
On 6 February 2013 16:03, Jan Matèrne (jhm) wrote:
> Maybe a table (feature x option):
>
> Feature|||
> Option | F1 | F2 | description
>
Claus, there is :). It's the -P validate profile in
platforms/karaf/features that caught it.
Yeah the cxf 2.6.6 features are pretty much unusable. I am sure Dan will
do something about it. Instead of reverting to 2.6.5 there is also the
option of copying the relevant features from cxf to camel
Am 09.02.13 09:12 schrieb "Claus Ibsen" unter :
>Should this commit also be done on trunk and 2.9 branch?
Hi Hadrian
I've got no clue what exact test failure you were facing with camel-msv.
Building it multiple times on my box I did not encounter any problems
before this dependency upgrade. Al
Should this commit also be done on trunk and 2.9 branch?
On Fri, Feb 8, 2013 at 9:55 PM, wrote:
> Author: hadrian
> Date: Fri Feb 8 20:55:43 2013
> New Revision: 1444236
>
> URL: http://svn.apache.org/r1444236
> Log:
> Upgrade xsdlib version and to fix test failure in camel-msv
>
> Modified:
>
On Sat, Feb 9, 2013 at 4:47 AM, Hadrian Zbarcea wrote:
> Fixed the msv issue and hit another one. Looks like the
> apache-cxf-2.6.6-features.xml [1] is invalid: ${cxf.james.mim4j.version} is
> not resolved :(.
>
Ah darn. CXF 2.6.5 does not have that issue, so in worst case we can
revert to this v
