rmannibucau commented on PR #791: URL: https://github.com/apache/maven/pull/791#issuecomment-1224239819
@slachiewicz a lot of plugins can - and do - rely on the provided slf4j-api at maven level (since most of the API is sadly exported and available using `ClassRealm` hierarchy). Upgrading to 2.x is not a transparent upgrade, in particular when the mojo overrides the binding (for good or bad reasons). This implies that functional logging will end up in something different (`No SLF4J providers were found.` for ex. Since for v4 `org.slf4j` must not be exposed (replaced by actual logging api and mojo related api) I think we should skip slf4j upgrade until we cleaned up our api leaks. -- 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
