[YARN-10563] Fix dependency exclusion problem in poms

• Type: Sub-task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.4.0
• Fix Version/s: 3.4.0
• Component/s: buid, resourcemanager
• Target Version/s: 3.4.0
• Hadoop Flags: Reviewed
• Assignee: Peter Bacsko
• Reporter: Peter Bacsko
• Created: 07/Jan/21 13:52
• Updated: 12/Feb/24 01:03
• Resolved: 12/Jan/21 14:30

Description

Currently, hadoop-project/pom.xml contains a bunch of exclusions for jsonschema2pojo-core. It turned out that when a project imports either hadoop-minicluster or hadoop-yarn-server-resourcemanager, excluded artifacts can actually show up as active dependencies. This is probably has to do with Maven as it does not handle exclusions properly when listed inside a dependencyManagement section. I confirmed it with some local builds (eg. Oozie uses hadoop-minicluster and the dependency tree showed a bunch of items that were not supposed to be there).

So all excludeable artifacts should be moved to hadoop-yarn-server-resourcemanager/pom.xml.