[
https://issues.apache.org/jira/browse/OAK-12093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18086569#comment-18086569
]
Julian Reschke commented on OAK-12093:
--------------------------------------
Here's another thing where need to be careful.
Consider a direct dependency, such as commons-lang, with version X.
When running in an OSGi container, we may want to test with version Y, where Y
< X (for instance because X behaves in a way so that that system
breaks/misbehaves; such as wiith commons-lang some time ago).
In our OSGi-ITs we thus want to test for compatibilty with version Y. In some
cases, the tests hardwire "Y", so it doesn't matter what the project selects.
But, if the POM used for the tests sets it's own version, it *does* matter.
> 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
> Attachments: duplicate-artifacts.md, parse_conflicts.py
>
>
> Currently many dependencies are declared explicitly in several modules and
> leads to pulling duplicate dependencies:
> The goal of this ticket is to rationalize and centralize as much as possible
> dependencyManagement to avoid these multiple versions.
> Current output of joined script analyzing dependency duplicates gives 37
> duplicate artifacts in the dependency tree : [^duplicate-artifacts.md]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
