Gary, As a reminder, a +1 vote means that the component will be marked deprecated in 2.x and removed in 3.x. This seems appropriate for log4j-spring-boot as users of Spring upgrading to Log4j 3.x will almost surely be on Spring Boot 3.
Ralph > On Nov 2, 2023, at 8:55 AM, Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > > Hi Gary, > > On Thu, 2 Nov 2023 at 16:30, Gary D. Gregory <ggreg...@apache.org> wrote: >> On 2023/11/02 15:05:05 "Piotr P. Karwasz" wrote: >>> On Thu, 2 Nov 2023 at 15:42, Gary Gregory <garydgreg...@gmail.com> wrote: >>>>> * `log4j-spring-boot`: >>>> -1: Spring seems too important. >>> >>> Are you sure you want to _veto_ a module removal based on a feeling? >>> `log4j-spring-boot` has 4 elements: a lookup, a property source, an >>> arbiter and an improved version of `Log4j2LoggingSystem`. >>> All these elements were submitted to Spring Boot by Ralph and included in >>> 3.x. >>> So this module targets the users that don't want Spring Boot 3.x, but >>> want Log4j 3.x. >> >> I feel it is too big an ask to force people to migrate to 3.x which is not >> released. > > I am not sure I am following. You don't want to force Log4j 3.x users > to migrate to Spring Boot 3.x? > I think the pressure to migrate to Spring Boot 3.x will be higher than > the pressure to migrate to Log4j 3.x. > > Piotr
