Hi
In the discussions about the ServiceMix future and the future of
ServiceMix features it was mentioned about moving some non-core features
into the Karaf Enterprise Features subproject. Another people think, the
Karaf subproject is not too good place for such features like Activiti.
Such features could be also extracted into a separate subproject in
ServiceMix which could have a separate lifecycle, but we don't have too
many such features to create a subproject for them.
In the code base for ServiceMix 6 (working version for the Karaf 3.x
line as not decided yet which version will have the SMX based on Karaf
3.x) I'd like to prepare 3 feature repositories
* servicemix-core - core features which will be integral part of
servicemix, not installable on other Karaf distributions
* servicemix-esb - non-core features like current Activiti integration
or missing connection factory for ActiveMQ. This repository should
provide features which will be used to build the ServiceMix
distribution and which can be also used outside the ServiceMix
distribution, e.g. in Karaf. It should have no dependency to core
ServiceMix. Currently we have not too many such features and some of
them could be moved into the original project or into the Karaf
Enterprise Features subproject (but id doesn't exist yet and many
people doesn't like the idea for moving the esb specific features
into Karaf). In the future we can have more esb features and we can
extract a separate subproject having own lifecycle,
* servicemix-examples - I think, the examples should be separated from
other features
What do you think about this idea?
Best regards and have a nice weekend
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
