You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Peter Bacsko (Jira)" <ji...@apache.org> on 2021/01/08 11:55:00 UTC
[jira] [Updated] (YARN-10563) Fix dependency exclusion problem in
poms
[ https://issues.apache.org/jira/browse/YARN-10563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Bacsko updated YARN-10563:
--------------------------------
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.
So all excludeable artifacts should be moved to {{hadoop-yarn-server-resourcemanager/pom.xml}}.
> 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
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Critical
>
> 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.
> So all excludeable artifacts should be moved to {{hadoop-yarn-server-resourcemanager/pom.xml}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org