Hi Perhaps we should have a separate subproject/repository for the enterprise features. The wouldn't block Karaf releases but could be updated after a new Karaf version is released (e.g. if the enterprise features need some dependencies included in standard Karaf features) or after a new enterprise library is released. Another solution would be such a repository as a SMX subproject. There is already repository for osgifying external bundles (Could be there committed any osgified libraries or should they be compatible with Apache license?). There could be something similar for enterprise features.
In my opinion the current Karaf enterprise features repository should still be part of Karaf as it is a integral part of Karaf and many other features depend on them. I mean we could have a separate subproject for any other 3rd party enterprise libraries which other users could use in their projects. I don't know whether all eterprise libraries fulfill the rules to be dependencies of Apache project. If no, It could be only a Github project. Regards Krzysztof On 27 February 2013 06:26, Andreas Pieber <[email protected]> wrote: > > > In general I still get a stall feeling in my stomage seeing all those > enterprise features. Keeping them directly at Karaf sounds like a bad idea. > We have already problems with the other enterprise features and their > versions (e.g. Spring). Maybe it's slowly getting time to decide how we > want to manage such external feature bundles? I add the dev list for CC to > get this question explicitly to the dev community. > >
