Page History

...

Here's a start at listing the proposed modules and their dependencies. These are proposed dependencies, their ; there currently there many cyclical dependencies. Part of the effort here will be to break required changes will breaking some of these cyclic dependencies by replacing hard coded references to other modules with plugins and callbacks that are part of the well defined API for each module.

...

Required changes: ?

Dunit

Package:dunit

API interface/classes: DistributedTestCase,CacheTestCase

...

This is still the big ball of string that needs to get untangled further. We need to split out  expiration, conflict detection, GII, transactions, partitioning, etc.

ResourceManager

Package: internal.cache.control

...

Probably not every package list here should be it's own gradle module. How will will enforce the dependencies and the use of the package interfaces.?

Package naming scheme

We still have a mix of two different conventions for where to put internal classes. Some things are in gemfire.internal.cache, and some things are in packages like cache.asyncqueue.internal. We should settle on one convention.

...