[
https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866301#comment-13866301
]
Vinod Kumar Vavilapalli commented on YARN-888:
----------------------------------------------
bq. 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.
Putting them in the non-leaf modules seems like a nice reuse of declaration of
common-dependencies. For e.g., if both NM and RM depend on something, I would
put it in server-common. That is not encouraged from now on? Both RM and NM
have to declare the dependency explicitly?
bq. This is causing issues in intellij IDE.
Putting dependencies in non-leaf modules breaks intellij IDE? That seems like a
bug in the IDE?
Please don't get me wrong, I'm trying to understand if we are doing the right
thing or not.
> 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)
