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 Sun, 05 Nov 2017 07:51:01 GMT

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

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

Ok, my direct use case is xbean (from geronimo) project. We do several shades and since asm
has now some module-info, we need to merge it properly. This use case is simple since we want
to export everything so can be a global toggle instead of fine merge. My "this week" workaround
will ve to exclude module info and use automatic module name since we need to release very
soon but a real shade solution is hoped for next releases.

Next big shades cases are meecrowave (from openwebbeans) where we shade several asf libs which
will all have module info file at some point.

Thinking out loud: is the exclude/automatic name workaround a first valid impl?

> 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