[
https://issues.apache.org/jira/browse/YARN-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911174#comment-13911174
]
Karthik Kambatla commented on YARN-745:
---------------------------------------
I would think moving classes between packages will be backwards compatible as
long as the canonical class name remains the same. All yarn jars are added to
the classpath, and the user shouldn't notice any difference. The dependencies
for a project might change, but the binaries built against an older version
should continue to work.
> Move UnmanagedAMLauncher to yarn client package
> -----------------------------------------------
>
> Key: YARN-745
> URL: https://issues.apache.org/jira/browse/YARN-745
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Fix For: 2.4.0
>
>
> Its currently sitting in yarn applications project which sounds wrong. client
> project sounds better since it contains the utilities/libraries that clients
> use to write and debug yarn applications.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
