[ 
https://issues.apache.org/jira/browse/MRESOLVER-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy updated MRESOLVER-64:
-----------------------------------
    Description: 
during work on MRESOLVER-36 to switch from LoggerFactory to direct slf4j, 
setLoggerFactory(...) methods were removed since they are not strictly required 
now

2 cases of removel (in {{DefaultArtifactResolver}} and 
{{DefaultRepositorySystem}}) broke Intellij IDEA Maven integration

adding back the method with empty implementation in the 2 classes, marking them 
deprecated, would restore strict API compatibility for older IDEA versions 
without much complexity

  was:
during work on MRESOLVER-36 to switch from LoggerFactory to direct slf4j, 2 
setLoggerFactory(...) methods were removed since they are not strictly required 
now
this broke Intellij IDEA Maven integration

adding back these methods with empty implementation, marking them deprecated, 
would restore strict API compatibility without much complexity


> restore setLoggerFactory(...) API deleted from version 1.3.0
> ------------------------------------------------------------
>
>                 Key: MRESOLVER-64
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-64
>             Project: Maven Resolver
>          Issue Type: Wish
>          Components: resolver
>    Affects Versions: 1.3.0, 1.3.1
>            Reporter: Hervé Boutemy
>            Priority: Major
>
> during work on MRESOLVER-36 to switch from LoggerFactory to direct slf4j, 
> setLoggerFactory(...) methods were removed since they are not strictly 
> required now
> 2 cases of removel (in {{DefaultArtifactResolver}} and 
> {{DefaultRepositorySystem}}) broke Intellij IDEA Maven integration
> adding back the method with empty implementation in the 2 classes, marking 
> them deprecated, would restore strict API compatibility for older IDEA 
> versions without much complexity



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to