+1 Having a library of ‘wrap’ descriptions also allows users to quickly wrap bundles without having to wait for a release.
-Matt > On Jun 19, 2023, at 8:38 AM, Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > > Hi Gert, > > It has been already discussed (I can seek for the thread, including > the board report). > > The idea is to move all into Karaf but using the new bundle/wrap > artifact handler. > The main difference is that we won't have any binary anymore: the > bundle will be created on the fly using a json descriptor doing > basically the same as SMX bundle maven build is doing. > The objectives are: > 1. avoid any legal issue as we don't wrap the original artifact, we > just describe how to create the corresponding bundle on the fly and > the user will do it at runtime (or build time by its own) > 2. one store the descriptors (no need of concrete releases) > > Regards > JB > > On Mon, Jun 19, 2023 at 12:41 PM Gert Vanthienen > <gert.vanthie...@gmail.com> wrote: >> >> 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
