Join GitHub today
Add starter and sample for Apache Geode. #5445
DO NOT MERGE (yet)! This PR is a preview for feedback only.
So, it turns out the
As further verification, my independent, example/test application declaring the
The problem is 1) the published Spring Data Maven BOM file has a hard version on the
Thus as I have done in the
I am thinking at this point, if there is no special Maven magic to work around this issue, then we might have to go with an actual, separate Spring Data GemFire dependency, as in spring-data-geode, making "Spring Data GemFire with Apache Geode support" a top-level module (i.e. Spring Data Geode) in the Spring Data portfolio.
Note, I cleaned up both #5444 and this PR by...
#5444 (polishing the GemFire starter/sample) is complete.
This PR still needs to sort out the
@olivergierke what say you?
Note, out of curiosity, I also observed that including the following in the
With the explicit
Pivotal GemFire is still used over Apache Geode in the
The only workaround is to put the above
Therefore, everything rides on creating a separate artifact (i.e. Spring Data Geode), or simply not having a Spring Boot Starter for Apache Geode. However, I do think it would be nice and convenient for our users.
DISCLAIMER: I know that we don't want to include the
Hi @wilkinsona -
There has only been recent mention of an official Apache Geode 1.0.0-incubating GA release. However, there is no current plan or schedule in place yet.
Still, both Apache Geode
Technically, the only reason why I have the newly minted Spring Data Geode module tagged as a milestone (i.e.
This PR to add support for Apache Geode has been updated with the latest release of Spring Data Geode
If you have questions, let me know.
referenced this pull request
Nov 5, 2016
@philwebb, @wilkinsona - I heard the message loud and clear on the SD Geode Caching and Repository support, but why does the Spring Boot "starter" for Spring Data Geode need to live outside of Spring Boot? If that is the case, then why do we include the spring-boot-starter-data-gemfire in Spring Boot? What's the difference?
The rule that we apply is that we only provide starters and samples for something if we also have auto-configuration for it. We've rejected other requests for starters and samples based on this rule and we need to apply it consistently. The GemFire starter is an exception to that rule for reasons that escape me. If we were doing things again, we wouldn't have that starter either.