Thanks Jinwoo for this contribution. I see you removed composite builds for custom plugins and switches to published artifacts, but this creates a problematic developer workflow needing devs to publish first before building. Cab we consider using includeBuild with proper dependency substitution or implement a task dependency that ensures plugins are published before use.
I left other comments on the PR. Sai On 2025/09/27 13:12:30 Jinwoo Hwang wrote: > Dear Apache Geode Community, > > A heartfelt thank you for the incredible support and initiative you’ve shown > for Apache Geode 2.0. It’s your collective energy and commitment that keep > this community vibrant and moving forward - each contribution powers the next. > > As part of the Apache Geode 2.0 initiative, we’re taking important steps to > modernize our build infrastructure. A new pull request, #7935, is now ready > for review, and your expertise would be greatly appreciated. > > Why this matters: > This PR focuses on migrating our build system to Gradle 7.6.6, which sets the > stage for a future upgrade to Gradle 8. This is a foundational change that > will help us: > > -Enable Future Upgrades: Prepares the codebase for Gradle 8 and beyond. > -Support Java 21 and Beyond on Gradle 8: Positions Geode to adopt the latest > Java features and maintain long-term compatibility. > -Improve Build Stability: Leverages fixes and improvements in Gradle 7.6.6 > for more reliable builds. > -Enhance Developer Experience: Provides better tooling compatibility and > modern build features. > -Reduce Technical Debt: Aligns with current Gradle standards for > maintainability. > > If you have time, please review the PR and share your feedback. Every > review—big or small—helps us move closer to a stronger, more modern Geode. > > Let’s keep the momentum going! > > > Best regards, > > Jinwoo Hwang (he/him/his) > > > > SAS® Research and Development > > http://JinwooHwang.com<http://jinwoohwang.com/> > > >
