[ 
https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17794151#comment-17794151
 ] 

ASF GitHub Bot commented on MNG-7532:
-------------------------------------

gnodet commented on PR #793:
URL: https://github.com/apache/maven/pull/793#issuecomment-1845227359

   > @gnodet well code was shared but you can review 
https://github.com/rmannibucau/mojo-logging-demo which is only about 2 cases 
(but there are more like using alpha version of slf4j or the opposite). Overall 
the outcome of discussions is that even if it would be simpler to leak all our 
internals (it is not only logging there), it is not really possible because we 
adopted an isolated architecture (realms) cause plugins have to do their stuff 
and we should just support it so we should isolated everything but the mvn4 api 
(status quo for mvn3).
   > 
   > side note: if this is no more assumed by most of community - I don't think 
it is the case but just highlighting what it means - we would have to drop the 
classrealm which wouldn't make much sense anymore and just request any plugin 
writer to fork for their work which rely on any other dependency than the ones 
we provide - don't think it is good but it is ultimately what we mean if we 
leak more and more.
   
   SLF4j api has been exported for more than 13 years, I haven't traced back to 
the very beginning though...




> 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/[email protected]/msg123452.html



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to