michael-o commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225894024
> > The client facing API of SLF4J is stable and has been stable since version 1.0. > > Not really 1.5->1.6 were not compat for ex (LocationAwareLogger#log, MessageFormatter, etc...). It hurt several apps already. So even I agree it is generally stable, it is not something we can assume for our _api_. It also increase the work needed to stay compatible since we have our own binding. > > It is really not "is slf4j bad" topic - in particular since it is fine to use it in @apache/maven core modules - but simply a design issue (we could workaround technical details if we would like to use it on a pure technical side), we should own our API to ensure mojo and extensions are reliable in time and not highly unstable (like gradle had been and was forced to introduce the wrapper to workaround it). You are mostly talking about impl, not API not. For the plugin dev.SLF4J simply works. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
