Hi all, What about creating a new karaf distro with the new configs? Not sure of the naming but idea is to have a "karaf-future" default setup, this way you get less surprises when it becomes the default. For all dev driven flow it will fit more (whereas the backward compatible default option fits better ops IMHO). Can't it enable to get the best of both worlds somehow?
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 ven. 8 janv. 2021 à 11:18, Jean-Baptiste Onofre <j...@nanthrax.net> a écrit : > Understood, and it makes sense. > > So, autoRefresh property will be present on 4.2.x and 4.3.x but still > "true" by default. > > And focus on Karaf 5 for some "conceptual" changes ;) > > Regards > JB > > > Le 8 janv. 2021 à 10:57, Robert Varga <n...@hq.sk> a écrit : > > > > On 08/01/2021 09:07, Grzegorz Grzybek wrote: > >> But summarizing, I'd keep autoRefresh=true in all the scenarios, where > >> Karaf is used as "application server" and switch it to > autoRefresh=false in > >> µservices / custom distro / single start mode. And looking forward > Karaf 5 > >> and new feature mechanism, I'd rather turn autoRefresh off in Karaf 5... > > > > +1. > > > > I would advise against changing behavior of 4.3.x -- it is exactly these > > sorts of changes which make even minor Karaf bumps a major uncertainty > > -- and have historically inflicted more frustration than I care to > > remember :( > > > > Regards, > > Robert > > > >
