[
https://issues.apache.org/jira/browse/HDFS-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13047471#comment-13047471
]
Eric Yang commented on HDFS-2063:
---------------------------------
When ivy check out common jar file for HDFS project, it used to be placed in
build/ivy/lib/Hadoop-Hdfs/common, but the project name is renamed by HDFS-560
to hadoop-hdfs. This is part one of the breakage. Part two is the test script
is looking for hard coded hadoop-common jar file. In neither cases, it is
unrelated to bin/lib changes broke the libhdfs test.
> Recent bin/lib changes broke the libhdfs test
> ---------------------------------------------
>
> Key: HDFS-2063
> URL: https://issues.apache.org/jira/browse/HDFS-2063
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.23.0
> Reporter: Eli Collins
>
> Looks like the recent bin/script shuffling in HDFS-1963 broke the libhdfs
> test. This works on 22.
> {noformat}
> $ ant -Dlibhdfs=true compile test
> ...
> [exec] Hadoop common not found.
> [exec] /home/eli/src/hdfs3/src/c++/libhdfs/tests/test-libhdfs.sh: line
> 181: /home/eli/src/hdfs3/bin/hadoop-daemon.sh: No such file or directory
> [exec] /home/eli/src/hdfs3/src/c++/libhdfs/tests/test-libhdfs.sh: line
> 182: /home/eli/src/hdfs3/bin/hadoop-daemon.sh: No such file or directory
> [exec] Wait 30s for the datanode to start up...
> {noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
