Is there an automated way to validate the need for the items in a given gradle.build?
Context: In large multi-product projects, gradle.build files can potentially get out of date as code is removed from a project, but the project’s gradle.build are not maintained. For example lets say a compile time dependency was listed on another project in a multi-project, but over time it’s usages have been deleted, but the deprecated dependcy is still listed unnecessarily in the gradle.build.
Is there an automated way to fish out this waste?