[
https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866923#comment-13866923
]
Vinod Kumar Vavilapalli commented on YARN-888:
----------------------------------------------
Makes sense now. I think I understand the main trouble point. I think this is
the one:
{quote} unless you only put in non-leaf POMs dependencies that are common to
all the leaf modules. {quote}
Today we put any dependency needed by *any* leaf-module in the non-leaf module.
That clearly adds a lot of burden on leafs that don't need those libs. Am I
understanding that correctly? If so, yeah, let's go for it. At the end of the
day, the deps that user sees needs to be as clean as possible.
> clean up POM dependencies
> -------------------------
>
> Key: YARN-888
> URL: https://issues.apache.org/jira/browse/YARN-888
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.0-beta
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Attachments: YARN-888.patch, YARN-888.patch, yarn-888-2.patch
>
>
> Intermediate 'pom' modules define dependencies inherited by leaf modules.
> This is causing issues in intellij IDE.
> We should normalize the leaf modules like in common, hdfs and tools where all
> dependencies are defined in each leaf module and the intermediate 'pom'
> module do not define any dependency.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
