maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Romain Manni-Bucau (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MSHADE-265) correct merging of module-info in shades
Date Sat, 04 Nov 2017 21:57:00 GMT

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

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

I know but it literally means "dont use shade plugin from now on" and "no migration of shade
usages". Im sure we - or oracle - can do something better, in particular with the fatjar/shade/uberjar
usage. At least we should provide a transformer with some include exclude config for all type
of module info entries.

> correct merging of module-info in shades
> ----------------------------------------
>
>                 Key: MSHADE-265
>                 URL: https://issues.apache.org/jira/browse/MSHADE-265
>             Project: Maven Shade Plugin
>          Issue Type: Improvement
>            Reporter: Romain Manni-Bucau
>            Priority: Trivial
>
> Should work by merging of the encountered module info jut also automatic module name
in manifest. The hard part being removing the not needed entries which are sometimes not simply
the ones of the included classes - SPI need it still



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message