[
https://issues.apache.org/jira/browse/OAK-12093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18086304#comment-18086304
]
Julian Reschke commented on OAK-12093:
--------------------------------------
Regarding jackrabbit components: I would only centralize those that we expect
to be used: jcr-commons, and jcr-spi (?).
Any other one should only appear in special cases like oak-upgrade. Having them
in the parent pom could cause the reader to wonder why it's in use in general
(at least that would be the case for me).
Same for dependencies that are only used in example projects.
> 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
>
> Currently many dependencies are declared explicitly in several modules and
> leads to pulling duplicate dependencies:
> Some examples are:
> 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
> 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)
