Fix Gradle deprecation warnings and implicit dependency issues #422
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fix Gradle deprecation warnings and implicit dependency issues to prepare for Gradle 8.0 compatibility.
This PR eliminates warnings that cause "Execution optimizations have been disabled" messages during builds, ensuring optimal build performance and future compatibility.
Build warnings fixed:
JavaExec.maindeprecatedmainClassNamedeprecatedConfigureUtildeprecatedChanges
Bug Fixes
dependsOn configurations.runtimeClasspathtodummytokens:jartask to fix implicit dependency onconfigs:jarRefactoring (Deprecation Fixes)
mainClassNameinscripts/java/tools/dummytokens/build.gradle→ useapplication { mainClass = ... }JavaExec.maininintegrations/spark/spark-3.1/openhouse-spark-runtime/build.gradle→ usemainClassBefore (warnings during build):
After (no warnings):
Testing Done
Manual Testing
./gradlew clean build -x test --warning-mode allNo Tests Added
This is a build infrastructure change that doesn't affect runtime behavior.
Additional Information
🤖 Generated with Claude Code