[
https://issues.apache.org/jira/browse/YARN-10563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan updated YARN-10563:
------------------------------
Component/s: buid
resourcemanager
Target Version/s: 3.4.0
Affects Version/s: 3.4.0
> Fix dependency exclusion problem in poms
> ----------------------------------------
>
> Key: YARN-10563
> URL: https://issues.apache.org/jira/browse/YARN-10563
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: buid, resourcemanager
> Affects Versions: 3.4.0
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Critical
> Fix For: 3.4.0
>
> Attachments: YARN-10563-001.patch
>
>
> 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}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
