[ https://issues.apache.org/jira/browse/MSHADE-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151278#comment-17151278 ]
Hudson commented on MSHADE-373: ------------------------------- Build failed in Jenkins: Maven TLP » maven-shade-plugin » master #106 See https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/master/106/ > Source transformation on source jar can break OSGi resolution due to > duplicated bundle name. > -------------------------------------------------------------------------------------------- > > Key: MSHADE-373 > URL: https://issues.apache.org/jira/browse/MSHADE-373 > Project: Maven Shade Plugin > Issue Type: Improvement > Affects Versions: 3.2.4 > Reporter: Rafael Winterhalter > Assignee: Romain Manni-Bucau > Priority: Critical > Fix For: 3.3.0 > > > Manifest transformers in the shade plugin are often used to add meta-data for > OSGi use since the shade and OSGi plugins are not overly compatible. If the > same transformer is applied to the source plugin's manifest, the resolution > will fail due to a duplicate bundle id. > It is therefore necessary to being able to opt-out of the manifest > transformer when shading a source file. > Pull request: [https://github.com/apache/maven-shade-plugin/pull/59] -- This message was sent by Atlassian Jira (v8.3.4#803005)