This becomes harder the larger your project is. If we didn't have gradle's transient dependency management, we would have to manually keep track of each dependency and resolve version conflicts by hand. This causes the project to contain multiple versions of the same class, and in turn causes the Dex tool to fail with the following error:Ĭom.TransformException: : duplicate entry: Resolving conflicts Who doesn't use apache-commons and GSon? Huh folks? Am I right? This guy knows what I'm talking about.Ī problem arises when the dependency is the same, but each module or library expects a different version. It is very common for for different modules and libraries to share the same dependencies. Invoking gradle dependencies -configuration compile results in something like this:Īlready we can learn that this project has a lot of dependency conflicts. For now let's look at a project's entire dependency tree. We'll get back to transitive dependencies in a second.
These trees tend to get complex as your project requires more and more libraries to compile.Ī direct, or "first level" dependency is one that you the developer explicitly import. Transitive dependency is an implied dependency, allowing your project to depend on libraries that depend on other libraries.
let's dive deeper into dependencies, direct and transitive, and gradle's dependency tools. My latest post discussed gradle's dependencyInsight task.
0 kommentar(er)
