[
https://issues.apache.org/jira/browse/HDFS-11596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15954473#comment-15954473
]
Andrew Wang commented on HDFS-11596:
------------------------------------
Thanks for the patch Yuanbo. I'm still thinking about this. The patch basically
changes hadoop-hdfs' dependency on hadoop-hdfs-client from compile scope to
provided, then fixed up other poms to refer to hadoop-hdfs-client with provided
or test scope where needed.
Overall, it seems okay. Applications shouldn't be depending on hadoop-hdfs
directly, so breaking them is okay (possibly good, as a prod to move to the
client deps). We also expect Hadoop deps like this to be on the classpath when
running Hadoop daemons.
That said, I am not a Maven expert, or super familiar with the expectations of
dist-layout-stitching.
[[email protected]], [~aw], any comments?
> hadoop-hdfs-client jar is in the wrong directory in release tarball
> -------------------------------------------------------------------
>
> Key: HDFS-11596
> URL: https://issues.apache.org/jira/browse/HDFS-11596
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: build
> Affects Versions: 2.8.0, 3.0.0-alpha2
> Reporter: Andrew Wang
> Assignee: Yuanbo Liu
> Priority: Critical
> Attachments: HDFS-11596.001.patch, HDFS-11596.002.patch
>
>
> Mentioned by [~aw] on HDFS-11356. The hdfs-client jar is in the lib directory
> rather than with the other hadoop jars:
> From the alpha2 artifacts:
> {noformat}
> -> % find . -name "*hdfs-client*.jar"
> ./share/hadoop/httpfs/tomcat/webapps/webhdfs/WEB-INF/lib/hadoop-hdfs-client-3.0.0-alpha2.jar
> ./share/hadoop/hdfs/sources/hadoop-hdfs-client-3.0.0-alpha2-sources.jar
> ./share/hadoop/hdfs/sources/hadoop-hdfs-client-3.0.0-alpha2-test-sources.jar
> ./share/hadoop/hdfs/lib/hadoop-hdfs-client-3.0.0-alpha2.jar
> ./share/hadoop/hdfs/hadoop-hdfs-client-3.0.0-alpha2-tests.jar
> {noformat}
> Strangely enough, the tests jar is in the right place.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
