dependency-analysis-gradle-plugin icon indicating copy to clipboard operation
dependency-analysis-gradle-plugin copied to clipboard

Guide to move dependencies from root project to modules need them

Open haihack opened this issue 3 years ago • 1 comments
trafficstars

Is your feature request related to a problem? Please describe. In multi-module projects that I didn't do in the first place, someone defined every dependencies in the gradle of root project instead of the module which is actually needs them. I'm always frustrated when finding which modules used the dependencies because in the report, it only says which modules not use them

Example: In these modules A, B, C, D. Among them, B is the only one use the dependency defined in the root gradle. In order to know it, in the report, I have to check in turn A doesn't use it B uses it C doesn't use it D doesn't use it

then move dependency from the root to B

It would be great if the report could guide me to move dependencies from root project to modules need them.

haihack avatar Sep 20 '22 02:09 haihack

I don't understand what you mean by "the dependency is defined in the root gradle." Could you clarify, ideally with a code snippet?

autonomousapps avatar Oct 10 '22 19:10 autonomousapps