If it does not break mojos (thinking to getLog API) +1 from me, otherwise I would be -1 until a compatibility module is properly added to the distro.
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 dim. 31 mai 2020 à 18:38, Tamás Cservenák <ta...@cservenak.net> a écrit : > +1 to rip out plexus logging > > On Sun, May 31, 2020, 17:58 Elliotte Rusty Harold <elh...@ibiblio.org> > wrote: > > > Moved from slack per suggestion: > > > > The documentation on logging for Maven seems of two minds: > > > > "Maven uses [Plexus logging API][6] with basic Maven implementation > > writing to stdout. > > We have reached the decision that SLF4J is the best option for a > > logging API: SLF4J has reached a certain level of ubiquity and while > > SLF4J may not be perfect, it's the de facto standard and it's > > pointless to try and remake another one. There are many > > implementations to choose from, including Logback and Log4j2. All the > > hard work has been done. All the bridges and funnels for other systems > > function well, which allows others to use whatever logging > > implementation they like in their components, while still being able > > to have integrated logging." > > > > Does this mean we can rip out the Plexus logging API and replace it > > with SLF4J? In at least one plugin, the plexus logging API pulls in a > > lot of plexus code we wouldn't otherwise need. > > > > -- > > Elliotte Rusty Harold > > elh...@ibiblio.org > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > >
