hadoop-tools | Tools for Hadoop -

If you have classes with same FQCN in 2 different jars and you want to keep using both in different scenarios (as they different by their Artifact Id), then best and clean way you can a achieve this is by breaking down into a separate module.

Please refer to Gradle Multi-Project builds

https://docs.gradle.org/current/userguide/multi_project_builds.html

In order to understand this behavior you need to understand how Spring DependencyManagement plugin works (see this section in the official documentation ):

• the dependencyManagement { } block is used to configure the contraints that will apply to the dependencies (version to use, exclusions for transitive dependencies, etc..) but this block will not apply itself these dependencies to you project,
• the dependencies of your project must be configured using the dependencies{ } block

In your example:

• first you have configured the dependencyManagement block in root project with constraints on "hadoop-common" and "hadoop-hdfs" modules, then you added contraint on "hadoop-tools" (using "dependency" or "dependencySet" in the dependencyManagement block): at this stage, you have not explicitly added any dependencies to your projects, but only configured the dependencies contraints

  ==> this explains why "hadoop-tools" dependency is not added/downloaded to your project.

• then you added a "compile" dependency on "hadoop-tools" using the dependencies block , which is the correct way to declare dependencies, and this made the "hadoop-tools" lib available in your project.

If I understand well your requirement, based on the source code you provided in the question: you could configure your projects as follow:

root project's script