[ 
https://issues.apache.org/jira/browse/YARN-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14074145#comment-14074145
 ] 

Zhijie Shen commented on YARN-2298:
-----------------------------------

I agree this is not an idea solution to split a package into two modules. 
However, there's a limitation that client module has dependency on rm module 
for the test scope, if I add rm module to depend on client module for the 
compile scope, it will be cyclic dependent. It is apparent that mvn doesn't 
consider scope when checking cyclic dependency. We met the same problem when we 
tried to make RM use NMClient to start AM container (though the work was not 
finished). Vinod and I have conducted some investigation, but didn't find a 
solution from mvn. If anybody knows the trick in mvn, please let us know.

> 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)

Reply via email to