[
https://issues.apache.org/jira/browse/RANGER-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17648394#comment-17648394
]
kirby zhou commented on RANGER-3860:
------------------------------------
I have a patch here to reduce about 210Mib of dist tarball size.
[https://reviews.apache.org/r/74258/]
> Huge unnecessary aws-java-sdk-bundle dependency
> -----------------------------------------------
>
> Key: RANGER-3860
> URL: https://issues.apache.org/jira/browse/RANGER-3860
> Project: Ranger
> Issue Type: Wish
> Components: Ranger
> Affects Versions: 3.0.0, 2.3.0
> Reporter: Aaron Braunstein
> Priority: Major
>
> RANGER-3653 added an aws-java-sdk-bundle dependency to Ranger, which causes
> the unpacked Ranger plugin jar size to increase by over 500 MB. Previously we
> only had an aws-java-sdk-logs dependency. There was no justification provided
> in the issue, but I suspect it was either due to a misunderstanding of how
> dependency management works in Maven, or because they wanted to avoid shading
> Ranger if there was some aws-java-sdk-logs 3rd party dependency that
> conflicted in version with some their project was already using.
> Aws-java-sdk-bundle relocates its dependencies.
> Aws-java-sdk-bom in dependency management (with scope import) did not add a
> dependency on all the aws java sdk's but only overrode the version of all aws
> sdk dependencies if it found one transitively or without a version defined,
> with the version supplied in the bom.
> I recommend that RANGER-3653 be reverted. Additionally, aws-java-sdk-logs
> version should be kept up-to-date to minimize version conflicts in libraries
> that are keeping their aws dependencies up to date.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
