You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2019/04/14 12:43:00 UTC
[jira] [Commented] (MSHADE-313) Minimize jar should respect
implementations under /META-INF/services/
[ https://issues.apache.org/jira/browse/MSHADE-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817296#comment-16817296 ]
Hudson commented on MSHADE-313:
-------------------------------
Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » master #4
See https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/master/4/
> Minimize jar should respect implementations under /META-INF/services/
> ---------------------------------------------------------------------
>
> 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
> Assignee: Robert Scholte
> Priority: Major
> Fix For: 3.2.2
>
> 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)