[
https://issues.apache.org/jira/browse/BEAM-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132026#comment-17132026
]
Beam JIRA Bot commented on BEAM-1720:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Consider minimization on shaded jars
> ------------------------------------
>
> Key: BEAM-1720
> URL: https://issues.apache.org/jira/browse/BEAM-1720
> Project: Beam
> Issue Type: Improvement
> Components: build-system
> Reporter: Aviem Zur
> Priority: P2
> Labels: stale-P2
>
> Some of our modules shade and relocate Guava as part of their build, this
> adds a considerable amount to their file size, even though they do not use
> every single class in Guava's jar.
> maven shade-plugin solves this by minimization which only shades classes
> which are in use in the module into the jar.
> There are a few issues with configuring minimzation for our shaded modules
> currently:
> 1. There is a bug in shade-plugin where if minimization is declared on a
> project with pom packaging it fails. I have created a
> [ticket|https://issues.apache.org/jira/browse/MSHADE-253] and
> [PR|https://github.com/apache/maven-plugins/pull/107] with a fix for this but
> could take a while before it is available to us (The fix has been merged but
> not released yet).
> 2. Minimization on all of our modules adds a significant amount of build
> time, which we wish to avoid. (Up from 02:30 mins for a build of the entire
> project (skipping tests) on a Macbook pro laptop to over 5 mins)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
