jxblum
commented
1 year ago Hi @erichaagdev - First, thank you for your contribution.
I have been meaning to let you know that all Spring for Apache Geode projects:
- Spring Boot for Apache Geode (SBDG; this project)
- Spring Session for Apache Geode (SSDG)
- Spring Test for Apache Geode (STDG; for which you also submitted a PR).
And even:
All of which, will reach OSS End of Life (EOL) by November 2023, once Spring Boot 2.x (specifically, 2.7.x) reaches OSS EOL (see here). There are no GA Spring bits for Apache Geode based on Spring Boot 3, Spring Session 3 or Spring Data 3.
Outside of customers who may have purchased a VSR license, and require immediate assistance with any of the Spring bits (and on Spring bits) for Apache Geode, this project is largely inactive, and no further development is occurring. Only critical bug fixes or CVEs are being addressed at this point, as necessary.
Though VMware did sponsor the Apache Geode project at ASF, VMW never supported OSS Apache Geode. For customers, this meant they needed to purchase a VMware GemFire license to get support. As of January/February this year, all Spring development for VMWare GemFire transitioned to the VMW Data Org, under the GemFire team.
erichaagdev
This pull request connects the build to the Gradle Enterprise instance at https://ge.spring.io/. This allows the Spring Boot for Apache Geode project to benefit from deep build insights provided by build scans and faster build speeds for all contributors as a result of remote build caching.
This Gradle Enterprise instance has all features and extensions enabled and is freely available for use by Spring Boot for Apache Geode and all other Spring projects. On this Gradle Enterprise instance, Spring Boot for Apache Geode will have access not only to all of the published build scans, but other aggregate data features such as:
Spring Boot, Spring Framework, and Spring Security are already connected to https://ge.spring.io/ and are benefiting from these features.
For these features to be made possible, appropriate access must be configured to publish build scans and to write to the remote build cache. To ensure a consistent experience for all Spring contributors, the Spring Gradle Enterprise Conventions plugin is used. Its documentation details how to configure credentials to publish build scans and for writing to the remote build cache.
Please let me know if there are any questions about the value of Gradle Enterprise or the changes in this pull request and I’d be happy to address them.