[
https://issues.apache.org/jira/browse/OAK-12093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18086256#comment-18086256
]
Julian Reschke commented on OAK-12093:
--------------------------------------
Lowering priority because:
* Build time gains would be lost in compilation/testing noise (in particular
when the maven repo is either local (default for developers or for CIs, close)
* Multiple versions sometimes can not be avoided (Tika, Lucene, Guava etc) for
now. For each of these we have (or should have) individual tickets.
* Transitive dependency mismatches can only be avoided by overriding the
dependency in the POMs, and really do not matter because they do not affect the
result (except for embeds which need to be considered separately).
For what's left we should open separate tickets and link them to this one (some
might already exist and can be linked to this one as well).
> 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: Minor
>
> 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)
