I'm a bit skeptical about a ServiceMix 8 release. That sounds really weird to me to release a new major version and announce just after it wont be supported. I doubt a lot of users will use it. In which case, it's time spent for nothing. I'd rather focus on the transition to Karaf document instead. Just my 2 cents.
Guillaume Le lun. 9 mars 2020 à 06:30, 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 > > -- ------------------------ Guillaume Nodet
