Avoid using `compile` configuration to declare dependencies in gradle build scripts
- Dominant language
- Kotlin
- Stars
- 249
- Forks
- 204
- PR merge metrics
- No merged PRs in 30d
Description
Currently on an exercise build Gradle reports a warning on the topic: `compile` configuration has been marked as deprecated for further removal.
Suppose we should substitute it with `implementation` in *_template*-ed and applied build scripts.
>The compile configuration has been deprecated for dependency declaration. This will fail with an error in Gradle 7.0. Please use the implementation configuration instead.
Contributor guide
No contributing guide indexed for this repository
Research direction
Inspect the exercise build scripts, including *_template*-ed and applied scripts, for dependency declarations using the deprecated compile configuration. Replace the relevant declarations with implementation, then run the Gradle build or exercise checks and confirm the deprecation warning is gone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100