Optimize Gradle tasks and configurations #3191
Draft
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.
Description
With the Gradle upgrades over time, some lines can be optimized and focus more on lazy initialization of only the necessary tasks to improve build times.
Solution
This PR applies some recommended refactorings to gradle files, including:
tasks.configureEach { ... }
instead oftasks.all { ... }
for task configurationtasks.register(...)
instead oftask ...
for task registrationThe commits aae5452 and 52b5ee4 can be backported to Solr 9.x.
Tests
No tests have been altered
Checklist
Please review the following and check all that apply:
main
branch../gradlew check
.