[
https://issues.apache.org/jira/browse/OAK-12093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18085423#comment-18085423
]
Julian Reschke commented on OAK-12093:
--------------------------------------
I'm still not convinced, and it sort of conflicts with
https://jackrabbit.apache.org/oak/docs/participating.html#pull-requests-prs.
In any case. I'm more than happy to split even the easy things the way I
suggested by myself (which should be ok, right)?
Of course that still leaves us with the question whether it makes sense to add
version variables to the parent POM when the dependency is only uses once. Yes,
they would be centralized, but on the other hand, it adds one level of
indirection when not needed.
I would suggest to start with the changes that actually solve a problem: when
different modules use different versions (for no good reason).
> 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)
