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 "Junping Du (JIRA)" <ji...@apache.org> on 2014/08/06 03:30:16 UTC
[jira] [Commented] (YARN-2298) Move TimelineClient to yarn-common
[ https://issues.apache.org/jira/browse/YARN-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087087#comment-14087087 ]
Junping Du commented on YARN-2298:
----------------------------------
Agree that cyclic dependencies between projects are disallowed, otherwise Maven doesn't know which project to build first. From what I know, the only way is to move the related code to somewhere else with several options: move it to a separated project, move it to RM or move it to some common place that both RM and client depend on. I would also prefer the third option just like [~zjshen]'s patch here as previous two options make no sense to me.
+1. Patch looks good to me. [~jianhe], do you have better way to handle it or additional comments? If not, I will go ahead to commit it later.
> Move TimelineClient to yarn-common
> ----------------------------------
>
> Key: YARN-2298
> URL: https://issues.apache.org/jira/browse/YARN-2298
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: client
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
> Attachments: YARN-2298.1.patch
>
>
> To allow RM to reuse the timeline client code, we have to move it out of yarn-client module, due to maven dependency issues.
--
This message was sent by Atlassian JIRA
(v6.2#6252)