Thanks JB! Yup, we also need to release specs before move. Such as jaxb-api 2.3 Cheers Freeman
On Sat, Mar 14, 2020 at 12:34 AM Jean-Baptiste Onofre <[email protected]> wrote: > Hi guys, > > Just a quick update about that. > > 1. I’m starting the preparation of the ServiceMix Bundles release for this > month. I plan to submit this release to vote middle of next week or so. > 2. I’m starting a migration guide draft on my GitHub (using md format) > that I will share with you. As Guillaume said, not sure a ServiceMix 8 > release makes sense. I think it’s worth to take time more on a migration > guide and assembly example. > 3. I’m also checking if some specs have to be released (it’s in relation > with the message I sent on the Karaf mailing list about spec features). > > I will keep you posted. > > Regards > JB > > > Le 9 mars 2020 à 06:29, Jean-Baptiste Onofre <[email protected]> a écrit : > > > > Hi everyone, > > > > Following the discussion about the "future" of ServiceMix, I would like > to propose the following plan: > > > > 0. Latest ServiceMix releases > > In order to give time to our users to "migrate" and move forward, I > think it makes sense to cut latest release and announce it would be the > latest one. > > In the coming two weeks, I will submit to vote: > > - ServiceMix Bundles release > > - ServiceMix 8 release (containing just version update) > > - Check if some spec bundles have to be released > > > > 1. ServiceMix Bundles move. As said, I started to work on a mechanism > storing the bundles descriptor. I started an improvement on pax-url-wrap > about that and the descriptors store would be new Karaf git repo (not need > of an individual vote, we can directly use the descriptor). > > As usage, it would look like: > > > > bundle:install wrap: > http://gitbox.apache.org/repos/asf/karaf-bundles/mybundle.json < > http://gitbox.apache.org/repos/asf/karaf-bundles/mybundle.json> > > > > Where the descriptor mybundle.json contains the location of the "base" > code, the statements, resources definition, etc (all that we have in the > ServiceMix bundles currently). > > > > For a community standpoint, I would propose to move interested > ServiceMix PMC as Karaf committer straight forward (I have to start a vote > on the Karaf community about that). Of course, if the committer is > committer and active, he will become Karaf PMC member. The reason why I > don’t want to just move the ServiceMix PMC as Karaf PMC is that lot of > ServiceMix PMC members are inactive now and I don’t want to "pollute" the > Karaf PMC. > > > > 2. Spec. Last week I sent a message on the Karaf mailing list related to > spec (especially with JDK 9+). As explained in this thread, Karaf should > provide spec features to be decoupled from JDK. In order to provide these > spec features, Karaf needs spec bundles, some spec are already bundles, but > some specs bundles are provided by Apache Geronimo or ServiceMix. > > The Spec OSGi Locator could be a module of Karaf itself (as it’s > embedded in the Karaf distributions). > > About the spec bundles, we can follow the pax-url-wrap way with the json > descriptor. > > > > 3. Once ServiceMix 8.0.0 is out, I would like to create a document > explaining how to "migrate" from ServiceMix to Karaf "ecosystem". The > purpose is to provide smooth path to ServiceMix users. I was thinking about > a Karaf Integration distribution (as stated in the first discussion > thread), but some of you said it’s not necessary. > > > > 4. Once those actions done, we will start a vote to move ServiceMix to > attic. > > > > In term of timeline, if you agree, I will move forward with ServiceMix > releases this week. > > About the "enhanced" pax-url-wrap, I would need couple of weeks to > finalize and polish this up. > > Wisely, we can plan to start the move to attic in couple of months. > > > > Thoughts ? > > > > Regards > > JB > > > >
