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

Romain Manni-Bucau commented on MSHADE-306:
-------------------------------------------

Sent https://github.com/apache/maven-shade-plugin/pull/10 to fix that issue, it 
is quite trivial but enables to investigate what went wrong more easily than 
debugging (in particular when it happens in a shade sent to Spark which was my 
case ;))

> 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
>            Priority: Major
>          Time Spent: 10m
>  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
(v7.6.3#76005)

Reply via email to