[
https://issues.apache.org/jira/browse/MSHADE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold resolved MSHADE-328.
------------------------------------------
Resolution: Not A Problem
> Implement 'automatic relocation of dependencies'
> ------------------------------------------------
>
> Key: MSHADE-328
> URL: https://issues.apache.org/jira/browse/MSHADE-328
> Project: Maven Shade Plugin
> Issue Type: New Feature
> Affects Versions: 3.2.1
> Reporter: Peng Cheng
> Priority: Major
> Labels: gradle, relocation, shading
> Original Estimate: 672h
> Remaining Estimate: 672h
>
> This feature intend to introduce the same feature in shadow plugin for gradle:
>
> [https://imperceptiblethoughts.com/shadow/configuration/relocation/#automatically-relocating-dependencies]
>
> package relocation is the only reliable defense against jar hell and usually
> can only be done at the final assembly stage (before that it is impossible to
> determine which package requires relocation). Thus, it cannot be conducted in
> a divide-and-conquer manner and requires enormous effort and a very complex
> process to be configured manually.
>
> Maven should automate this process by analyzing the dependency tree and
> relocate package whenever there is a version conflict
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
