[
https://issues.apache.org/jira/browse/MNG-8176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873024#comment-17873024
]
ASF GitHub Bot commented on MNG-8176:
-------------------------------------
rmannibucau commented on PR #1336:
URL: https://github.com/apache/maven/pull/1336#issuecomment-2284631812
> In most cases, slf4j is not a problem.
Well, from my perspective we decided to use maven.api logging api and let
the mojo use or not another API/binding/solution so there is no more reason to
let slf4j leak (or then we should let leak other stuff too).
Slf4j was not a problem until it became and the choice was to give more
guarantees to the mojo writers so default is probably better not having it and
use tuning options to let it pass in unsafe mode.
But just my 2 cts indeed.
> Restrict class loaders for Maven 4 plugins
> ------------------------------------------
>
> Key: MNG-8176
> URL: https://issues.apache.org/jira/browse/MNG-8176
> Project: Maven
> Issue Type: New Feature
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Priority: Major
> Fix For: 4.0.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
