maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <j...@apache.org>
Subject [jira] [Commented] (MRESOLVER-64) restore API deleted from version 1.3.0
Date Tue, 04 Dec 2018 23:55:00 GMT

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

Hervé Boutemy commented on MRESOLVER-64:
----------------------------------------

method added back to the 2 classes that broke IDEA: https://github.com/apache/maven-resolver/commit/b2eeafe26d5901abbdf341d2d8c6d68f08c5a99b

looking at MRESOLVER-36 fix https://github.com/apache/maven-resolver/commit/e1976767cf714da24336339f7a6286c6ab50986a
, there are many other locations where equivalent method has been removed without having known
impact

should we add back these methods just for safety while at it?

> restore 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, 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



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

Mime
View raw message