[BEAM-1720] Consider minimization on shaded jars

• Type: Improvement
• Status: Open
• Priority: P3
• Resolution: Unresolved
• Component/s: build-system
• Assignee: Unassigned
• Reporter: Aviem Zur
• Created: 14/Mar/17 20:38
• Updated: 03/Jun/22 17:20

Description

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 and PR 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)

Issue Links

• is blocked by: MSHADE-253 NullPointerException if minimizeJar == true && packaging == pom