I agree that there is a potential. Though I prefer a clear stance on the status of a repository: is a thing yet or not? It has been dormant for 7 years already and there is no clear future commitment. Unless somebody is certain that it will be picked up in a matter of months, I am in favor of archiving the repository. If it is deemed to be necessary, we can always activate it later I guess.
On Wed, Sep 13, 2023 at 4:01 PM Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > Hi Volkan, > > On Wed, 13 Sept 2023 at 15:34, Volkan Yazıcı <vol...@yazi.ci> wrote: > > > > `logging-log4j-boot` <https://github.com/apache/logging-log4j-boot>, > last > > touched 6 years ago, is a spin-off from LOG4J2-1775 > > <https://issues.apache.org/jira/browse/LOG4J2-1775>, where it is stated > > that *"The Log4j Boot concept can be superseded by the increased > > modularization being done in 3.0. No longer relevant."* I want to archive > > this repository. Objections? > > I see `log4j-boot` as a possibly light alternative to the logging part > of Spring Boot. > > While configuring a logging backend with most APIs requires just the > right dependencies on the classpath, users might still need some > programmatic help to configure JUL. > > IMHO Log4j Boot could do just that, i.e. check if Logback or Log4j > Core are on the classpath and either: > * set the appropriate `LogManager` property if it is not too late, > * or configure a JUL handler to forward everything to the right API. > > Piotr >
