[
https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738726#comment-17738726
]
ASF GitHub Bot commented on MNG-7532:
-------------------------------------
rmannibucau commented on PR #793:
URL: https://github.com/apache/maven/pull/793#issuecomment-1613609202
> We can not expect that all code in plugins only use Maven and JDK API,
thirt party library used in plugins code can uses any logging framework.
Sure and we comply to that, only thing is that end user can only expect
maven logging framework to be integrated with maven ecosystem (think CI and
maven customizations) so if the plugin provider wants something well integrated
it has to use that.
frontend maven plugin forwarded node logs to maven logging system for that
to give an example.
> It should not be important what logging framework is used in Maven core.
Probably a good wish but factually it is.
> Technically we can forward logging message from one framework to another
and it can be transparent for plugins code.
Good wish too but there are several cases which are not trivial. Personally
I see it as limitations when deployed inside maven and most plugins have work
arounds for that so all good, but we are not neutral enough (as the JVM is) to
support anything.
It is more or less the same than we are not 100% isolated between plugins -
classloader is partially only, env is almost not isolated etc...
Not sure about the spring reference but it is the same, they work in some
env but not always and this is ok.
The only thing maven guarantees is that the plugin API will go through maven
logging system so if integration is customized it will get the logs, anything
else is not guaranteed - except JUL by construction indeed.
> Revert MNG-6931 deprecation since list shows no consensus on that
> -----------------------------------------------------------------
>
> Key: MNG-7532
> URL: https://issues.apache.org/jira/browse/MNG-7532
> Project: Maven
> Issue Type: Task
> Reporter: Romain Manni-Bucau
> Priority: Major
>
> There are several threads on the dev list asking for the drop of slf4j and at
> least keeping a logging abstraction for not internal dev (= core can use
> slf4j but not mojo/extensions).
> Work is being done to abstract plugin api so let's keep the
> deprecation/replacement of our Log API in this track and keep it the official
> way for now.
> one of the multiple refs:
> https://www.mail-archive.com/dev@maven.apache.org/msg123452.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
