Gradle find unused dependencies

Provides advice for managing dependencies and other applied plugins. Dependencies declared on the wrong configuration api vs implementation vs compileOnlyetc. These side effects are currently mostly undocumented internal behaviors, but they may be interesting for some advanced users. In addition to the dependency-related advice see aboveDAGP provides other advice to gradle find unused dependencies maintain your "build health.

This is a follow-up to The proper care and feeding of your Gradle build , in which I wrote about how to use the Dependency Analysis Gradle Plugin to help maintain a healthy build for your Android, Java, and Kotlin projects. In this first of a series of posts, we will discuss how that plugin works. To begin, we will take a look at bytecode analysis with the ASM library, and how it is essential in the detection of unused dependencies. In future posts, you can expect discussions of source code parsing with ANTLR, introspecting jars for capabilities such as service loading and annotation processing, dependency management with Gradle APIs, and more. This is a complex question. And what even is a dependency? It provides a collection of zero or more:.

Gradle find unused dependencies

You can add dependencies and view them in the diagram. Any dependency added to the project is managed by Gradle. The best way to add or manage a dependency is in the build. From the context menu, select Add Maven artifact dependency. The Maven Artifact Search window opens. In the Maven Artifact Search window, in the search field, start typing the name of your dependency. In the list of results select the one you need and click Add. Reload your project. If you add a dependency configuration of the source set , it will be displayed in the Gradle tool window as well. You can work with Gradle dependencies in the diagram format. It might be helpful when you have a large project and want to see the whole picture of how dependencies including the transitive ones are connected inside the project. In the Gradle tool window, select a project, on the toolbar, click or select the Show Dependencies option from the context menu. To close the popup, press Escape. Use the diagram window toolbar to manage the diagram. You can change the size of a diagram, export it to a file, see only a part of the diagram you are interested in, and so on.

Click Structure in the left toolbar. At the top level are all the dependencies you've declared directly, but below those are the transitive dependencies the top-level or direct dependencies depend on; these are gradle find unused dependencies available for direct use, despite not being declared by your project.

.

In June, , they have released the 4. They have also added Android support to unused-dependency. In May Gradle has implemented the Gradle lint plugin for finding and removing unwanted dependency. The Gradle Lint plugin is a pluggable and configurable linter tool for identifying and reporting on patterns of misuse or deprecations in Gradle scripts and related files. This plugin has various rules. Unused Dependency Rule is one of them.

Gradle find unused dependencies

In Gradle dependencies are libraries required to build your code. Each of these libraries may have their own dependencies, adding transitive dependencies to your project. This structure is called the Gradle dependency tree , with its own rules on dependency conflict resolution and more.

Monna haddid leak

There is no advice regarding this dependency. You can see the analysis in its full glory at asm. Knowing if a dependency is used for compilation Not to belabor the point, but this is a complex question. Build health. Use the context menu to zoom in and out, move canvas, change layout, and export part of the diagram into an image. More advanced usage. Are you sure you want to hide this comment? Not to belabor the point, but this is a complex question. In the diagram window, select a dependency you need. Go to file. Toggle to display the list of dependencies in a form of nodes or in the flat list. It does do some limited analysis of runtime dependencies such as noting if a dependency provides Java ServiceLoader s , but otherwise elides this domain. Releases tags. Any dependency added to the project is managed by Gradle.

This is a follow-up to The proper care and feeding of your Gradle build , in which I wrote about how to use the Dependency Analysis Gradle Plugin to help maintain a healthy build for your Android, Java, and Kotlin projects.

It might be helpful when you have a large project and want to see the whole picture of how dependencies including the transitive ones are connected inside the project. You can get a sense for the things that matter from the parameter names, however. In the Maven Artifact Search window, in the search field, start typing the name of your dependency. Subprojects "modules" that unnecessarily use the Android plugin, and could instead by "normal" JVM libraries. BufferedSource implies api. Log in Create account. The Artifact in this case is a custom data type that wraps a jar file on disk. Alternatively, in the Gradle tool window, right-click the needed dependency and select Analyze Dependencies from the context menu. The Maven Artifact Search window opens. There is no advice regarding this dependency. And what even is a dependency? From the list, select the dependency scope you want to see.