As discussed on IRC, ServiceMix should provide more unit tests,
especially around Camel and CXF used in OSGi.
First, I'm gonna update to Camel 2.6-SNAPSHOT and CXF 2.3-SNAPSHOT in
preparation of the upgrade. It should be ready tonight (GMT+1 time).
After that, I'm gonna work on it. If you need some are that should be
spotted in the unit tests, please keep us posted.
Any help is welcome.
Regards
JB
On 01/17/2011 03:55 PM, Daniel Kulp wrote:
On Monday 17 January 2011 9:31:33 am Hadrian Zbarcea wrote:
Camel 2.6 is almost ready for a release. The last hudson test [1] only had
4 failures in camel-scala (looks like the problem wasn't fully resolved by
Willem, and the problem still exists in the current build [2]). It looks
like everything else is really stable and I'd suggest not committing
patches that may impact stability until the release is voted. I'll look at
the scala issue too and that should be fixed today, so tomorrow we should
be ready for the builds.
From what I see, SMX is looking forward to using camel 2.6 with cxf 2.3.2
which is being built now. Should we wait another 2-3 days and release
camel-2.6.0 with cxf upgraded to 2.3.2? I saw Willem, Gert, Johan and JB
involved in that discussion. Guys, since you understand the options and
implications best, what's your suggestion?
Well, I really think if anyone that will be using Camel and CXF together in an
OSGi environment is really going to need the OSGi related fixes in 2.3.2.
There's just a bunch of things that won't work correctly in OSGi with 2.3.1.
Thus, if Camel uses 2.3.1, anyone running in OSGi will likely need to override
it anyway. I suggest waiting a couple days.
Dan
Hadrian
[1] https://hudson.apache.org/hudson/job/Camel.trunk.fulltest/119/
[2]
https://hudson.apache.org/hudson/job/Camel.trunk.fulltest/120/org.apache.c
amel$camel-scala/
On Jan 16, 2011, at 3:45 AM, Claus Ibsen wrote:
Thanks Christian
All tickets for Camel 2.6 has now been resolved. So lets give the CI
servers some time to test it.
If all is well early next week, then Hadrian can start cutting the
release.
Thanks for all the hard work on this release. Its another staggering
250+ tickets resolve release.
And great contributions from the community.
On Sun, Jan 16, 2011 at 9:37 AM, Christian Müller
<christian.muel...@gmail.com> wrote:
I reverted the changes for
https://issues.apache.org/jira/browse/CAMEL-3311and closed this issue.
I will implement this feature in a better solution in
Camel 2.7 with
https://issues.apache.org/jira/browse/CAMEL-3515<https://issues.apache.
org/jira/browse/CAMEL-3311> .
