I meant following:
* If we want to start ServiceMix 5 again from the beginning (by
removing the current code base and creating a new custom Karaf 3.x
distribution) we could do following instead:
o we could release ServiceMix 5 in the current form (with Karaf
2.3 or 2.4) if we think ServiceMix is stable and we don't want
to remove the current work
o start ServiceMix 6 from the beginning using Karaf 3.x
But if there is no reason to release ServiceMix 5 in the current
form we can restart ServiceMix 5 with Karaf 3.x
* if we want only to upgrade ServiceMix 5 (without restarting the
sources) then ServiceMix 5 should be upgraded to Karaf 3.x.
On 14.02.2014 11:55, Cristiano Costantini wrote:
I've not understood clearly, you would base SMX5 on Karaf 2.3.3 and SMX6 on
Karaf 3.0.0 ?
I prefer to align major version upgrades to those of Karaf, so SMX 4.x on
Karaf 2.x and SMX 5 on Karaf 3,but any of the two is good for me.
2014-02-14 11:06 GMT+01:00 Krzysztof Sobkowiak <[email protected]>:
I prefer the solution with restart of the ServiceMix code base and build
it from scratch based on Karaf 3.x (we could use the new plugins and the
new configuration files from Karaf). But I saw the current version of
ServiceMix 5 has been updated to the newest version of Karaf 2.3.x and the
problems I had when I was trying to perform the upgrade to 2.3.3 was only
caused by the sclala library.
I haven't fully tested ServiceMix 5, but the samples I have tested make no
problems. When ServiceMix 5 is almost stable perhaps we could fix the
existing issues and release it in this form (based on Karaf 2.3.x, probably
upgraded later to Karaf 2.4.x) and start ServiceMix 6 from scratch based on
Karaf 3.x and Karaf features. I think people have made some good work to
make ServiceMix5 and perhaps we shouldn't send it into /dev/null :) What do
you think about this?
Regards
Krzysztof
--
Krzysztof Sobkowiak
JEE & OSS Architect | Technical Architect @ Capgemini
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
e-mail: [email protected] <mailto:[email protected]> |
Twitter: @KSobkowiak
