[
https://issues.apache.org/jira/browse/HBASE-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796592#action_12796592
]
Kay Kay commented on HBASE-1433:
--------------------------------
So far -after hdfs repositories have been published to apache snapshot
repository - ran this patch locally , that completes test without the dynamic
link issue with the following caveats.
* The jars in hadoop-mapred/0.21.0 seem to be corrupted.
* Checked out branch ( branch-0.21) of mapreduce . manually created the jars
(hadoop-mapred and hadoop-mapred-test) and copied them to
~/.ivy2/org.apache.hadoop/hadoop-mapred(-test) to circumvent ivy . Dynamic
link issue disappeared (great !!)
* org.apache.hadoop.hbase.TestInfoServers FAILED (timeout)
$ cat build/test/TEST-org.apache.hadoop.hbase.TestInfoServers.txt
Testsuite: org.apache.hadoop.hbase.TestInfoServers
Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
Testcase: testInfoServersAreUp took 0.003 sec
Caused an ERROR
Timeout occurred. Please note the time in the report does not reflect the time
until the timeout.
junit.framework.AssertionFailedError: Timeout occurred. Please note the time in
the report does not reflect the time until the timeout.
But that might be a different issue altogether independent on dependency
management that we can handle separately . may be.
* TODO: Fix MAPREDUCE-1352 with revised checkin to branch and revised
publishing of artifacts. That should resolve this issue.
> Update hbase build to match core, use ivy, publish jars to maven repo, etc.
> ---------------------------------------------------------------------------
>
> Key: HBASE-1433
> URL: https://issues.apache.org/jira/browse/HBASE-1433
> Project: Hadoop HBase
> Issue Type: Task
> Affects Versions: 0.20.2
> Reporter: stack
> Attachments: HBASE-1433.patch, HBASE-1433.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
