L.S.,
Seeing Willem's question on the discussion of the future of the main assembly, made me think about what we should be doing with the other two remaining ServiceMix projects. For the specs, we already have a karaf-specs project, so I'm not sure we need to do anything. If we need a new release of one of the existing ServiceMix specs, we can just move that spec to the karaf-specs and do the release there. I'm not sure if there's any added value in moving all of our existing/old specs over to that project. For the bundles, I'm aware people are working on an improved solution for creating bundles for existing JARs. I also noticed however that we have done quite a few bundles releases in the meanwhile and we might have to do quite a few more before the new solution is ready. Those bundle votes also seem to have a hard time getting enough people to look into those in the ServiceMix project. Would it be an idea to move all of our existing bundles over to a karaf-bundles project? We can probably just make a script that changes group id/package names/... to org.apache.karaf in bulk, so the only real effort would be in writing that script and holding the votes to move the codebase over to the Karaf project. Another option could be to create a similar script to only copy & rename a single bundle from servicemix-bundles to karaf-bundles. That way, we can start with an empty karaf-bundles project and move the bundles over one by one when we need a new release for them, similar to the approach I mentioned for the specs project. This second approach probably makes a bit more sense, since we have tons of old bundle versions that will probably never get released again, so there's no point in dragging those along. We should probably discuss this on the Karaf dev@ list as well, but I wanted to bring it up here first. Wdyt? Regards, Gert Vanthienen
