[
https://issues.apache.org/jira/browse/YARN-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13872235#comment-13872235
]
Sean Mackrory commented on YARN-1601:
-------------------------------------
+1 (non-committer) - I can confirm the problem from a Bigtop perspective. If
you were to try and build the "hadoop-client" package it would break because
there wouldn't be any other Hadoop package that would provide one of the
dependencies Maven determined was needed for a YARN client (specifically,
stax-api 1.0-2, which has a different group ID than stax-api 1.0.1).
> 3rd party JARs are missing from hadoop-dist output
> --------------------------------------------------
>
> Key: YARN-1601
> URL: https://issues.apache.org/jira/browse/YARN-1601
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 3.0.0, 2.4.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Attachments: YARN-1601.patch
>
>
> With the build changes of YARN-888 we are leaving out all 3rd party JArs used
> directly by YARN under /share/hadoop/yarn/lib/.
> We did not notice this when running minicluster because they all happen to be
> in the classpath from hadoop-common and hadoop-yarn.
> As 3d party JARs are not 'public' interfaces we cannot rely on them being
> provided to yarn by common and hdfs. (ie if common and hdfs stop using a 3rd
> party dependency that yarn uses this would break yarn if yarn does not pull
> that dependency explicitly).
> Also, this will break bigtop hadoop build when they move to use branch-2 as
> they expect to find jars in /share/hadoop/yarn/lib/
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
