[
https://issues.apache.org/jira/browse/OAK-12093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18085801#comment-18085801
]
Benjamin Habegger commented on OAK-12093:
-----------------------------------------
1: Originally, in February, doing a build with a fresh local maven repository.
Some grep magic on the download URLs to extract the downloaded artifacts and
their versions. Some sorting and grouping to identify which artifacts had
duplicates.
2: I got the numbers by doing the same thing on the branch. and comparing
before and after (original numbers still in the PR)
Retried recently but this is tedious, because the build is long and flaky by
itself, but also because I commute. I got an AI to have a look and will post
it's finding on the PR as markdown is nice there.
> Improve build by rationalizing dependencies
> -------------------------------------------
>
> Key: OAK-12093
> URL: https://issues.apache.org/jira/browse/OAK-12093
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: Benjamin Habegger
> Priority: Major
>
> In the current pom setup some dependencies are being downloaded multiple
> times:
> Jackson: 2.13.5, 2.17.3
> Zstd: versions 1.5.5-5, 1.5.6-3, 1.5.7-4, 1.5.7-6
> Gson: 2.10.1, 2.11.0, 2.5, 2.9.0, 2.9.1
> Error_prone_annotations: 2.11.0, 2.18.0, 2.26.1, 2.27.0, 2.3.4, 2.41.0
> j2objc-annotations: 1.3, 2.8, 3.0.0
> This increases the volume of downloaded artifacts and thus the build time.
>
>
> The goal of this ticket is to rationalize and centralize as much as possible
> dependencyManagement to avoid these multiple versions
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
