Hi Willem,
We needn't release whole set of components, we can release components
independently. That's also one important goal to refactor the project
structure (extract compoents as project), another important goal I think
is share the components between different version of SMX container.
Regards
Freeman
Willem Jiang wrote:
AFAIK, Camel 1.5 is now waiting for the CXF 2.1.3.
I am planing to release CXF 2.1.3 this week, so SMX 4.0-m2 and camel can
use the same CXF version.
BTW, I just want to ask a question, since current SMX voting components
are using CXF 2.1.2. If we want to CXF bc and se components to use CXF
2.1.3, do we need to release the whole components or just release CXF bc
and se components.
Thanks,
Willem
Freeman Fang wrote:
Hi Guillaume,
About SMX 4.0-m2, is it possible that we use camel 1.5 and cxf 2.1.3,
which both are under release process as I know.
Regards
Freeman
Guillaume Nodet wrote:
I think we need to release a few more things:
* NMR 1.0.0-m3 (it contains a very important improvement wrt to
lifecycles of JBI endpoints deployed with the OSGi packagin)
* New set of bundles
* Apache ServiceMix 4.0-m2 (requires bundles, nmr + components under
vote)
* Apache ServiceMix 3.3 (require components under vote)
* Apache ServiceMix 3.2.3 ?
I will start the NMR release this week and will follow with 4.0-m2.
Any volunteer for the other releases ?
