[
https://issues.apache.org/jira/browse/HDFS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759614#action_12759614
]
Doug Cutting commented on HDFS-641:
-----------------------------------
> If not, what are the alternative suggestions?
Perhaps we just need a higher-level build file, so that the standard working
pattern is something like:
{noformat}
svn co https://svn.apache.org/repos/asf/hadoop/build/trunk .
svn co https://svn.apache.org/repos/asf/hadoop/common/trunk common
svn co https://svn.apache.org/repos/asf/hadoop/hdfs/trunk hdfs
svn co https://svn.apache.org/repos/asf/hadoop/mapreduce/trunk mapreduce
ant test-hdfs
ant test-mapreduce
{noformat}
If you want to test against a different version, then checkout its branch or
tag, or unpack its tarball. The test-mapreduce and test-hdfs targets would
first build both hdfs and mapreduce, then build and run tests.
> Move all of the benchmarks and tests that depend on mapreduce to mapreduce
> --------------------------------------------------------------------------
>
> Key: HDFS-641
> URL: https://issues.apache.org/jira/browse/HDFS-641
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 0.20.2
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Priority: Blocker
> Fix For: 0.21.0
>
>
> Currently, we have a bad cycle where to build hdfs you need to test mapreduce
> and iterate once. This is broken.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
