[
https://issues.apache.org/jira/browse/GEODE-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Rhomberg resolved GEODE-6169.
-------------------------------------
Resolution: Fixed
> Use Spring Dependency-Management to streamline dependency versioning
> --------------------------------------------------------------------
>
> Key: GEODE-6169
> URL: https://issues.apache.org/jira/browse/GEODE-6169
> Project: Geode
> Issue Type: Improvement
> Components: build
> Reporter: Patrick Rhomberg
> Assignee: Patrick Rhomberg
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Our use of the `dependency-versions.properties` is cumbersome, hard to read,
> and bloats the global namespace of the gradle project.
> Ideally, we would use the {{constraints}} configuration of our dependencies,
> but per the documentation
> [here|https://docs.gradle.org/current/userguide/managing_transitive_dependencies.html],
> POMs produced using this feature are incorrect (including {{scope}} in the
> {{dependencyManagement}} section of the pom).
> With {{22a5017745acd4ca22cbcb08b70cc3cedbb4b5fd}} / GEODE-6117, a small
> use-case of this library was introduced to streamline geode-client BOM
> generation.
> This library would be useful to apply to each of our subprojects, allowing
> simpler declaration of dependencies and eliminate the mix-and-match approach
> of explicit definition or delegation to {{project.'some-library.version'}}
> that seems pervasive.
> Lastly, this will integrate with the Nebula dependency linter (GEODE-5801),
> as the linter is currently unable to detect unused dependencies in the face
> of our concatenated string convention.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
