Because Spring Data GemFire with Apache Geode support (apache-geode) is not part of the Spring Data Release Trains (e.g. Fowler, Gosling, Hopper, etc) it makes more sense to maintain a constant and stable dependency on both Spring Data Build and Spring Data Commons, respectively. Until Apache Geode has an official GA release, SDG with Apache Geode support cannot progress along with the other SD modules during pre-release, development milestones (e.g. M1, RC1) since Apache Geode does not maintain a predictable and similar release cycle. Therefore, it makes sense that SDG with Apache Geode support be coupled with the Apache Geode release cycle until the first GA release. At which time, SDG with Apache Geode support can then maintain a constant, fixed dependency on Apache Geode, as a 'driver' (similar to SDG with Pivotal GemFire support, which depends only on GA GemFire releases) and subsequently, be sync'd with the SD Release Train.
184f05bf30