Hello, Up-front disclaimer: I'm not a Gradle expert - but I spent a little time poking around at what it would take to upgrade the build to go from Gradle 6.8 -> Gradle 7.4
Previous efforts to clean up Gradle 7 deprecation warnings made it fairly straightforward - in the end it seems there were only a few changes needed. - An internal gradle class for the temporary file creation changed it's package location in Gradle 7 - A couple places had references to the now-removed "compile" classpath and needed to be replaced with "compileOnly" - Gradle 7 gets upset about tasks that have implicit dependencies between them - some of the tasks such as the combined report generation needed to have a "dependsOn" added to it - The Geode build has a custom version of the "DefaultTaskExecutor" - Gradle made some minor changes to the DefaultTaskExecutor in version 7.4. I made those same changes in the RepeatedTaskExecutor On my local machine the build runs the same as it does on the 6.8 version - there are some tests that fail due to bind exceptions. I just created a draft pull request - like I mentioned before, I'm not the world's leading expert in Gradle so there may be a better way to make some of the same kind of changes. I created a draft pull request so that it might at least serve as a starting point when someone else wants to take a look at this. https://github.com/apache/geode/pull/7351 I didn't see a JIRA issue directly associated with this, it's sort of related to GEODE-9161 <https://issues.apache.org/jira/browse/GEODE-9161> since it gets rid of the deprecation warnings. Hope it's helpful, Ryan
