[
https://issues.apache.org/jira/browse/MSHADE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17086335#comment-17086335
]
Romain Manni-Bucau commented on MSHADE-306:
-------------------------------------------
[~md_5] hmm, you rarely want the one of your project when doing a shade, you
loose all meta of transitive deps which breaks OSGi and a good number of OSS
libraries putting versions and other data there. That said you can include your
own artifact to not exclude it I guess. If not it is fine to simplify the
include/exclude mecanism for me (maybe a "enforceArtifactFiles=true|false")
rather than ignoring errors IMHO.
> Log all duplicates, not only classes
> ------------------------------------
>
> Key: MSHADE-306
> URL: https://issues.apache.org/jira/browse/MSHADE-306
> Project: Maven Shade Plugin
> Issue Type: New Feature
> Reporter: Romain Manni-Bucau
> Assignee: Romain Manni-Bucau
> Priority: Major
> Fix For: 3.2.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Issue to silently swallow duplicated resources is that you don't see, even in
> debug, that there is a choice done by the plugin. This breaks the final app
> in a lot of cases (all SPI-like cases, OSGi for the MANIFEST.MF etc...). So
> let's log it as for classes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
