Switch to 'runtimeClasspath' instead of resolve 'implementation' configuration.
In PR #69 the build.gradle was updated to run on Gradle 7, part of the change consisted in
forcing the resolution of 'implementation' configuration to use it in the listing of dependencies.
This could be assolved by the 'runtimeClasspath' without forcing the resolution which smells like a trick.
Why is it important/What is the impact to the user?
Not directly impact the user
Checklist
[x] My code follows the style guidelines of this project
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have made corresponding change to the default configuration files (and/or docker env variables)
[ ] I have added tests that prove my fix is effective or that my feature works
Author's Checklist
[x] verify ./gradlew clean vendor is ok, and required_jars.rb doesn't change
Release notes
[rn:skip]
What does this PR do?
Switch to 'runtimeClasspath' instead of resolve 'implementation' configuration.
In PR #69 the build.gradle was updated to run on Gradle 7, part of the change consisted in forcing the resolution of 'implementation' configuration to use it in the listing of dependencies. This could be assolved by the 'runtimeClasspath' without forcing the resolution which smells like a trick.
Why is it important/What is the impact to the user?
Not directly impact the user
Checklist
I have commented my code, particularly in hard-to-understand areasI have made corresponding changes to the documentationI have made corresponding change to the default configuration files (and/or docker env variables)I have added tests that prove my fix is effective or that my feature worksAuthor's Checklist
./gradlew clean vendoris ok, and required_jars.rb doesn't changeHow to test this PR locally
Related issues