Big +1, and the good point about Romain’s proposal is that we have two different subproject:
- Karaf OSGi runtime where we can focus on the tooling, etc - Karaf runtime manager where we can focus on runtime, multi runtime tooling, assembly Regards JB > Le 4 nov. 2020 à 10:51, Francois Papon <francois.pa...@openobject.fr> a écrit > : > > Agree and we have to focus on building the distribution and testing easily. > > regards, > > François > fpa...@apache.org > > Le 04/11/2020 à 10:21, Jean-Baptiste Onofre a écrit : >> Changing the "perspective/cursor" with Karaf as "runtime backbone", where >> OSGi is a kind of runtime, at same level as spring-boot, micro profile, >> whatever, is actually very interesting. >> >> It could gives "perspective" to the project: >> - Karaf OSGi runtime >> - Karaf runtime manager >> >> I like the idea ;) >> >> Regards >> JB >> >>> Le 4 nov. 2020 à 09:39, Romain Manni-Bucau <rmannibu...@gmail.com> a écrit : >>> >>> This is a very interesting approach and I wouldn't keep OSGi a backbone but >>> one of the supported runtime (as spring-boot, microprofile or even >>> javaee...oops jakartaee, why not?). >>> So overall OSGi flavor would be a karaf 4 in a karaf 5 to illustrate the >>> idea. >>> Being able to aggregate runtimes in a single JVM has a great value but it >>> must not come with all the build requirements (and prerequirements to tests >>> for instance) so something lighter than OSGi, probably closer to >>> tomcat/servlet classloading default model (parent with the "container", >>> children with the apps) makes a lot of sense. >>> I wouldn't call it karaf 5 (please dont do AMQ5-AMQ6 error), but as karaf >>> is the industrialization of an OSGi runtime it makes sense to have an >>> industrialization of a generic runtime, it is the next step IMO and I >>> already envision the "merge" of a docker-compose/k8s recipe with 10 >>> uservices in a single JVM, financial department will love it and dev will >>> keep doing what they want, everybody will be happy ;). >>> >>> Romain Manni-Bucau >>> @rmannibucau <https://twitter.com/rmannibucau> | Blog >>> <https://rmannibucau.metawerx.net/> | Old Blog >>> <http://rmannibucau.wordpress.com> | Github >>> <https://github.com/rmannibucau> | >>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book >>> <https://www.packtpub.com/application-development/java-ee-8-high-performance> >>> >>> >>> Le mer. 4 nov. 2020 à 08:52, Grzegorz Grzybek <gr.grzy...@gmail.com> a >>> écrit : >>> >>>> śr., 4 lis 2020 o 08:35 Jean-Baptiste Onofre <j...@nanthrax.net> >>>> napisał(a): >>>> >>>>> That’s a great feedback ! >>>>> >>>>> Today, we are "challenged" by other approach. I still believe that we >>>> have >>>>> a great asset in the runtime ecosystem. >>>>> >>>>> My thinking now is more to still use OSGi internally (and let people do >>>>> OSGi on Karaf if they want) but open the scope to other >>>> framework/approach >>>>> (spring boot, micro profile, etc). We would embrace a wider community and >>>>> expend our use cases. >>>>> With François, I think we already identified some improvements patch >>>>> (lighter/immutable runtime, tooling, …), but I would love to have >>>> feedback >>>>> from the community to drive the roadmap. >>>>> >>>>> Thanks Greg ! You made my day ;) >>>>> >>>> :) >>>> I'll definitely think outside of OSGi box after I finish my current >>>> assignment (work). >>>> >>>> regards >>>> Grzegorz >>>> >>>> >>>>> Regards >>>>> JB >>>>> >>>>>> Le 4 nov. 2020 à 07:43, Grzegorz Grzybek <gr.grzy...@gmail.com> a >>>> écrit >>>>> : >>>>>> śr., 4 lis 2020 o 07:41 Jean-Baptiste Onofre <j...@nanthrax.net> >>>>> napisał(a): >>>>>>> What do you mean by "impossible" ? Removing OSGi from the picture, or >>>>>>> thinking about Karaf future ? ;) >>>>>>> >>>>>> I meant I see OSGi everywhere and that's all I do for last 6+ years, so >>>>>> it's hard for me to NOT think about OSGi ;) >>>>>> If I was asked to help shaping Karaf 5, I'd still think OSGi-first... >>>>>> >>>>>> regards >>>>>> Grzegorz Grzybek >>>>>> >>>>>> >>>>>>> Regards >>>>>>> JB >>>>>>> >>>>>>>> Le 4 nov. 2020 à 06:27, Grzegorz Grzybek <gr.grzy...@gmail.com> a >>>>> écrit >>>>>>> : >>>>>>>>> don’t think OSGi focus >>>>>>>>> >>>>>>>> For now it's impossible for me ;) Looks like I need some OSGi-REST... >>>>> ;) >>>>>>>> regards >>>>>>>> Grzegorz >>>>>>>> >>>>>>>> śr., 4 lis 2020 o 06:16 Jean-Baptiste Onofre <j...@nanthrax.net> >>>>>>> napisał(a): >>>>>>>>> Hi >>>>>>>>> >>>>>>>>> Not yet, I’m working locally on changing the structure. >>>>>>>>> >>>>>>>>> And I don’t want to be influenced or influence for now ;) >>>>>>>>> >>>>>>>>> So, I would love your overall thinking in term of approach, >>>> features, >>>>>>>>> vision, and again generally speaking (don’t think OSGi focus, or one >>>>>>>>> particular use case, more global). >>>>>>>>> >>>>>>>>> Regards >>>>>>>>> JB >>>>>>>>> >>>>>>>>>> Le 4 nov. 2020 à 06:09, Grzegorz Grzybek <gr.grzy...@gmail.com> a >>>>>>> écrit >>>>>>>>> : >>>>>>>>>> Hello >>>>>>>>>> >>>>>>>>>> Great news! Is this branch already available in Karaf's git repo? >>>>>>>>>> >>>>>>>>>> regards and stay safe! >>>>>>>>>> Grzegorz Grzybek >>>>>>>>>> >>>>>>>>>> śr., 4 lis 2020 o 05:59 Jean-Baptiste Onofre <j...@nanthrax.net> >>>>>>>>> napisał(a): >>>>>>>>>>> Hi guys, >>>>>>>>>>> >>>>>>>>>>> François and I started to think about Karaf 5 and give an even >>>>> modern >>>>>>>>>>> flavor to Karaf, including potentially lot of refactoring and >>>>> changes. >>>>>>>>> We >>>>>>>>>>> think it’s a must have in our patch to the "main modulith >>>> runtime". >>>>>>>>>>> Before sharing all details (some have been shared during my talk >>>> at >>>>>>>>>>> ApacheCon), we want to move forward on a PoC branch. >>>>>>>>>>> >>>>>>>>>>> However, we would love to have your inputs and thoughts (think >>>> wide >>>>>>> ;)). >>>>>>>>>>> So, please, if you have ideas, comments, criticism ;), send me an >>>>>>> email >>>>>>>>>>> and I will reply and eventually include your points in the PoC. >>>>>>>>>>> >>>>>>>>>>> Thanks ! >>>>>>>>>>> Regards >>>>>>>>>>> JB >>>>>>>>> >>>>>>> >>>>>
