[GEODE-5801] Make module dependencies explicit, rather than relying on exposed elements from other modules.

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: build
• Assignee: Unassigned
• Reporter: Patrick Rhomberg
• Created: 01/Oct/18 20:49
• Updated: 01/Oct/18 20:49

Description

This ticket is intended to be a "parent" for the wide-reaching work of making our dependencies within a given module more explicit.

See this thread on the dev list for discussion surrounding the intentionality of exposing dependencies.

Sub-Tasks

• Code Cleanup: remove pathological geode-core test source set assignment.: Resolved
• Improve checkPom utility, add gradle task to update expectedPoms: Resolved
• As much as possible, a gradle file should have only one dependencies block.: Resolved
• Add geode-core exclusion from all geode-junit and geode-dunit dependencies: Resolved
• Make extension module dependencies explicit.: Resolved
• Make dependencies explicit in geode-lucene, *-old-client-support: Resolved
• Make dependencies explicit in geode-pulse: Closed
• Make dependencies explicit in geode-protobuf: Resolved
• Make dependencies explicit in cq and rebalancer modules: Resolved
• Make dependencies explicit in connectors and experimental-driver modules: Resolved
• Make dependencies explicit in geode-wan: Resolved
• Add Nebula dependency linter to the gradle build.: Resolved
• Dependencies should not be injected into every subproject by test.gradle: Closed
• Combine dependencies into dependencySets: Resolved
• Remove resource coupling between geode-core test sets: Open
• Add task to linter to ensure that all dependencies listed are consumed. Remove those unused version declarations.: Open
• Identify root cause for gradleLint.ignore xml-apis: Open