Hi Dennis-

For a schedule of the Spring releases, you can have a look at the Spring
release calendar (https://spring-calendar.cfapps.io/).

Note, these are tentative (but fairly accurate) dates.  Things shift around
(occasionally) when a upstream project (dependencies) gets delayed (bugs,
CVEs, etc).

Also, I have created version for Spring Data GemFire [1]; I will make it a
point to do the same for Spring Data Geode.

Thank you for your patience.

Regards,
John

[1]
https://github.com/spring-projects/spring-data-gemfire/wiki/Spring-Data-GemFire-to-GemFire-Version-Compatibility


On Tue, Apr 17, 2018 at 9:18 AM, Dennis Dai <[email protected]> wrote:

> Great, thanks for the info! I will just stick with 1.2.1 for now.
>
> Dennis Dai
> [email protected]
>
> On Apr 16, 2018, at 8:38 PM, John Blum <[email protected]> wrote:
>
> Dennis-
>
> SDG 2.0.6.RELEASE (SD Kay-SR6) is based [1] on Apache Geode 1.2.1.  SDG
> 2.0.x cannot be bumped to a different minor version of Apache Geode (e.g.
> 1.2 -> 1.3/4/5) due to issues like you found.
>
> SDG 2.1.0 (SD Lovelace), currently at 2.1.0.M2 (SD Lovelace-M2) is based
> [2] on Apache Geode 1.4, currently.
>
> I recently updated SDG 2.1.0 to the newly minted Apache Geode 1.5
> (DATAGEODE-95 [3], branch [4]), but due to issues in Apache Geode 1.5 (e.g.
> GEODE-5039 [5], etc), I am waiting to bump the version to Apache Geode 1.6,
> when available, which will most likely be picked up in SDG 2.1.0.M3 (SD
> Lovelace-M3).
>
> -j
>
>
> [1] https://github.com/spring-projects/spring-data-geode/blo
> b/2.0.6.RELEASE/pom.xml#L25
> [2] https://github.com/spring-projects/spring-data-geode/blo
> b/2.1.0.M2/pom.xml#L25
> [3] https://jira.spring.io/browse/DATAGEODE-95
> [4] https://github.com/spring-projects/spring-data-geode/tre
> e/DATAGEODE-95/upgrade-to-apache-geode-1.5
> [5] https://issues.apache.org/jira/browse/GEODE-5039
>
>
> On Mon, Apr 16, 2018 at 6:27 PM, Dennis Dai <[email protected]> wrote:
>
>> Hello,
>>
>> I recently upgraded to SDG 2.0.6 and Geode 1.5.0 but I am having
>> NoClassDefFoundError when starting up a client application, here is part of
>> the exception:
>>
>> Caused by: org.springframework.beans.factory.BeanCreationException:
>> Error creating bean with name 'gemfireCache': FactoryBean threw exception
>> on object creation; nested exception is java.lang.NoClassDefFoundError:
>> org/apache/geode/internal/cache/RegionService
>> at org.springframework.beans.factory.support.FactoryBeanRegistr
>> ySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:170)
>> at org.springframework.beans.factory.support.FactoryBeanRegistr
>> ySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:101)
>> at org.springframework.beans.factory.support.AbstractBeanFactor
>> y.getObjectForBeanInstance(AbstractBeanFactory.java:1645)
>> at org.springframework.beans.factory.support.AbstractAutowireCa
>> pableBeanFactory.getObjectForBeanInstance(Abstr
>> actAutowireCapableBeanFactory.java:1178)
>> at org.springframework.beans.factory.support.AbstractBeanFactor
>> y.doGetBean(AbstractBeanFactory.java:327)
>> at org.springframework.beans.factory.support.AbstractBeanFactor
>> y.getBean(AbstractBeanFactory.java:199)
>> at org.springframework.beans.factory.support.BeanDefinitionValu
>> eResolver.resolveReference(BeanDefinitionValueResolver.java:367)
>> ... 101 more
>>
>> I checked Geode repo and noticed that Geode removed
>> org.apache.geode.internal.cache.RegionService at v1.4.0 and if I revert
>> back to v1.3.0 the app started up without issues. So is there a highest
>> Geode version cap that can be used with SDG?
>>
>> Thanks,
>>
>> Dennis Dai
>> [email protected]
>>
>>
>
>
> --
> -John
> john.blum10101 (skype)
>
>
>


-- 
-John
john.blum10101 (skype)

Reply via email to