This message was deleted.
# community-support
s
This message was deleted.
s
It’s not Android, though..
But maybe that doesn’t matter
d
It works also on normal Java projects
👍 1
v
The Android in the name is just bad initial name choosing. But actually the plugin does the opposite of what you asked for was what you asked for is bad practice
It tells you libraries you depend on but don't use and it tells you libraries you use but don't declare but for just have as transitive dependencies and some more.
s
Yeah, I noticed that. We have a lot of explicit dependencies in build.gradle files in various projects that I don’t think should be there. Some of those would probably be covered by the “unused” detection here, so that’s great! I don’t necessarily agree that what I’m trying to accomplish is bad practice, but I have no need to discuss that right now, just looking for the tools. 🙂
As a simple example, I don’t think it would be a good idea to have a dependency on
org.springframework.boot:spring-boot-starter-web
and then also a explicit one on
org.springframework:spring-web
. I want the dependencies that are tested together as the Spring Boot package.
v
Yeah, ok, for things like Spring Boot it is slightly different, as its purpose is to use the transitive dependencies. For that you can define in the dependency analysis plugin that it is ok to use dependency X transitively from dependency Y, so you don't get a complaint.