[
https://issues.apache.org/jira/browse/OAK-12093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18085418#comment-18085418
]
Benjamin Habegger commented on OAK-12093:
-----------------------------------------
Splitting individually each dependency one by one just to move the version
management to the parent pom really feels like too much. I don't see the strong
benefit of over complicating things while I do see the benefit of moving
forward.
This said, I agree we could split, but I don't see the benefit of going so fine
grained. If we really want a split, I would propose:
* one task for "easy" versions : this ticket
* one task per "tricky" case: e.g. tika, lucene, and the "embedded" cases (but
there I would need you to be more explicit)
And, yes, updating is important as well, maybe more so, but centralizing will
in fact help upgrading and managing version. So we could also see this work as
preparatory to help upgrading.
> 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)
