Hi
Yeah Karaf is a bit more tricky, as just because the feature file
validates succesful, and the features can be installed one by one in
Karaf, does not mean that they actually work.
We do have a bunch of integration tests in camel-itest-osgi but not
for every components.
So in this case camel-
Thanks Claus, I wasn't aware of this issue. May I overlooked the JIRA?
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member
https://www.linkedin.com/pub/christian-mueller
It is good to avoid minor dependency updates in Camel micro releases,
and this should be kept as true as possible especially with main
dependencies,
but with the big fauna of dependencies of the project it is best to have
flexibility over this rule to avoid paralysis :-)
A better commit message ho
camel-fop doesnt work in karaf without this upgrade.
On Fri, Oct 18, 2013 at 1:08 AM, Christian Müller
wrote:
> I thought we agreed to not do minor dependency updates in Camel micro
> releases.
>
> Best,
> Christian
> Am 17.10.2013 09:29 schrieb :
>
>> Updated Branches:
>> refs/heads/camel-2.
I thought we agreed to not do minor dependency updates in Camel micro
releases.
Best,
Christian
Am 17.10.2013 09:29 schrieb :
> Updated Branches:
> refs/heads/camel-2.12.x 6eea01095 -> faff7402f
>
>
> upgrade fop 1.0 to 1.1
>
>
> Project: http://git-wip-us.apache.org/repos/asf/camel/repo
> Comm
