[
https://issues.apache.org/jira/browse/MRESOLVER-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16714222#comment-16714222
]
Dan Tran edited comment on MRESOLVER-64 at 12/10/18 4:03 AM:
-------------------------------------------------------------
I am able to reproduce this issue with instructions from Rostislav Krasny and
[~slachiewicz]
The issue is fixed then hook it up with my local maven 3.6.1-SNAPShOT + new
version of resolver
was (Author: dantran):
I am able to reproduce this issue with instructions from Rostislav Krasny and
[~slachiewicz], then hook it up with my local maven 3.6.1-SNAPShOT + new
resolver
> 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
> Assignee: Hervé Boutemy
> Priority: Major
> Fix For: 1.3.2
>
>
> 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 removal (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)