maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Karg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MSHADE-313) Less agressive <minimizeJar>
Date Thu, 28 Mar 2019 22:54:00 GMT

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

Markus Karg commented on MSHADE-313:
------------------------------------

Tests still in progress, but initial draft of the PR is already online as WIP at [https://github.com/apache/maven-shade-plugin/pull/17].
Stay tuned. :)

> Less agressive <minimizeJar>
> ----------------------------
>
>                 Key: MSHADE-313
>                 URL: https://issues.apache.org/jira/browse/MSHADE-313
>             Project: Maven Shade Plugin
>          Issue Type: Improvement
>    Affects Versions: 3.2.1
>            Reporter: Markus Karg
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The maven shade plugin already does a great job in minimizing JAR size. For the majority
of applications this is exactly what is needed.
> On the other hand there are some application areas where the algorithm is too agressive.
One particular and rather frequently found case is the services API: ServiceLoader will ceise
to work for minimized JARs since it is the prototype of the biggest "minimize-JAR-antipattern":
String-to-class conversion.
> To make <minimizeJar> usable in such scenarios, there should be a set of options
to enable the usual suspetcs (like ServiceLoader) to be detected.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message