gnodet commented on PR #793:
URL: https://github.com/apache/maven/pull/793#issuecomment-1613621466
> > 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.
If we:
* provide a simple abstraction for mojo (the current Log)
* export major APIs (commons-logging and slf4j
* redirect those, in addition to JUL
This should cover most basic cases.
If course, libraries that do setup specifically a logging framework, it will
most certainly not be integrated, but we can't do much about that.
--
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
