[
https://issues.apache.org/jira/browse/MSHADE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313924#comment-17313924
]
Markus Karg commented on MSHADE-385:
------------------------------------
Romain, sorry for the confusion. I double-checked MSHADE and in fact it is
working pretty-well with MJARs. My fault simply was that I forgot to
_explicitly_ provide `<Multi-Release>true</Multi-Release>` in MSHADE's manifest
transformer config, as I assumed that MSHADE would do that _automatically_ once
it detects a `version` folder in one of the shaded dependencies. Silly me. ;)
> Support for Multi-Release-JARs
> ------------------------------
>
> Key: MSHADE-385
> URL: https://issues.apache.org/jira/browse/MSHADE-385
> Project: Maven Shade Plugin
> Issue Type: New Feature
> Affects Versions: 3.3.0
> Reporter: Markus Karg
> Priority: Major
>
> Maven Shade Plugin currently is unable to deal with multi-release JARs, hence
> it always (and only) picks the lowest commen nominator (fallback) class.
>
> Actually the plugin should instead produce a multi-release JAR, hence pick
> all class versions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
