You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2022/10/13 10:28:00 UTC

[jira] [Commented] (MINDEXER-167) Drop shading for indexer-core

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

Hudson commented on MINDEXER-167:
---------------------------------

Build succeeded in Jenkins: Maven » Maven TLP » maven-indexer » master #63

See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-indexer/job/master/63/

> Drop shading for indexer-core
> -----------------------------
>
>                 Key: MINDEXER-167
>                 URL: https://issues.apache.org/jira/browse/MINDEXER-167
>             Project: Maven Indexer
>          Issue Type: Task
>            Reporter: Tamas Cservenak
>            Assignee: Tamas Cservenak
>            Priority: Major
>             Fix For: 7.0.0
>
>
> Shading is getting more and more problematic, and it is actually "indexer consumer" who can/should decide what to shade. The indexer-core shading shaded only Lucene in (and caused issues like MINDEXER-107), while it left SLF4J and many other "potential clashing" dependencines unshaded. As there is no "one size fit all" for shading, best is to remove shaded artifact alltogether, and let consumers shade as best suits them, if they want to.



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