[ 
https://issues.apache.org/jira/browse/GEODE-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16723549#comment-16723549
 ] 

ASF subversion and git services commented on GEODE-6198:
--------------------------------------------------------

Commit 411b22cdd1d87f1c55f81de948ff36f421a893af in geode's branch 
refs/heads/develop from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=411b22c ]

GEODE-6198: Add geode-all-bom for dependency versioning (#2995)

* Introduce dependency management via geode-dependency-management.gradle
* All relevant modules refer to the BOM to determine dependency versions.
* Consequently, all compile tasks depend on the BOM.  Because several 
non-compile tasks will also require the BOM, it is registered as a dependency 
for all DefaultTask type tasks -- essentially all tasks.  While currently 
heavy-handed, this can be iterated against in future PRs.
* Explicit versioning from dependency declarations, deferring to the BOM 
specification.
* Other cleanups: unify Spring plugin usage; bump version to 1.0.6 release; 
move eclipse configurations outside of dependency blocks, as they are unrelated.
* Prune most of now-redundant dependency-versions.properties.  Those lingering 
elements should be removed in a future PR.
* Update relevant expected POMs
* Update expected jars list.  This should likely not include those compile-only 
classpath elements, to be addressed in a future PR.

Co-authored-by: Dick Cavender <dcaven...@pivotal.io>
Co-authored-by: Patrick Rhomberg <prhomb...@pivotal.io>

> Manage dependencies via BOM
> ---------------------------
>
>                 Key: GEODE-6198
>                 URL: https://issues.apache.org/jira/browse/GEODE-6198
>             Project: Geode
>          Issue Type: Improvement
>            Reporter: Patrick Rhomberg
>            Assignee: Patrick Rhomberg
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to