[
https://issues.apache.org/jira/browse/MSHADE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17086156#comment-17086156
]
md_5 commented on MSHADE-306:
-----------------------------
Romain,
It's still problematic because in most cases you will want to use the
META-INF/MANIFEST.MF of *your* project, but adding an exclude filter on
{code:java}
*:* {code}
Will mean that you lose the manifest of your project (if it was created by
maven-jar-plugin or similar)
> 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)
