[
https://issues.apache.org/jira/browse/OAK-12093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18085461#comment-18085461
]
Julian Reschke commented on OAK-12093:
--------------------------------------
My suggestion is to first identify cases in which Oak itself appears to use
different versions. This can be a problem when different sub projects test with
differing versions (with different bugs, for instance).
In some cases this can be intentional; in OSGi tests we sometimes use an older
version in order to check whether the Oak components are compatible with what
the "target" OSGi container (ahem) will have.
FWIW, Filevault has an interesting concept where tests are run both with the
oldest version supported and the newest ones. (But that does not scale 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: 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)
