[
https://issues.apache.org/jira/browse/MINDEXER-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965374#comment-17965374
]
Olivier Lamy commented on MINDEXER-167:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-indexer#584|https://github.com/apache/maven-indexer/issues/584].
> Drop shading for indexer-core
> -----------------------------
>
> Key: MINDEXER-167
> URL: https://issues.apache.org/jira/browse/MINDEXER-167
> Project: Maven Indexer (Moved to GitHub Issues)
> 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)
