autonomousapps / autonomousapps/dependency-analysis-gradle-plugin
Report unnecessary excludes
- Dominant language
- Kotlin
- Stars
- 2.2k
- Forks
- 158
- Avg merge
- 16h 25m
- Merged PRs (30d)
- 46
Description
You can exclude certain dependencies from being reported as unused but then when that excluded dependency actually gets removed from the project, the unnecessary exclude declaration is still there unnecessarily. It would be nice if the plugin could detect those cases and suggest a configuration change. Android Lint does a similar thing with issues included in its baseline file but no longer present in the project.
Contributor guide
Research direction
The issue does not name files or tests. Start by locating the plugin's unused-dependency exclusion reporting and compare its behavior with the Android Lint baseline analogy. Done means stale excludes are detected and reported with actionable configuration advice, with tests covering the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100