[ http://issues.apache.org/jira/browse/HADOOP-356?page=all ]
Michel Tourn updated HADOOP-356:
--------------------------------
Attachment: buildallcontribs.patch
The patch unblocks HADOOP-307
The patch modifies the following targets:
<target name="clean-contrib" depends="compile">
<target name="compile-contrib" depends="compile-core">
<target name="compile" depends="compile-core, compile-contrib">
<target name="test" depends="test-core, test-contrib">
<target name="test-contrib">
--
How to add a new "contrib" project:
add a subdirectory to src/contrib/<projectname>
see src/contrib/streaming/build.xml for an example build.xml
There are generic ant targets in src/contrib/build.xml and build-contrib.xml
To disable a contrib target:
put an excludes attribute in src/contrib/build.xml (explained inside)
> Build and test hadoopStreaming nightly
> --------------------------------------
>
> Key: HADOOP-356
> URL: http://issues.apache.org/jira/browse/HADOOP-356
> Project: Hadoop
> Issue Type: Improvement
> Reporter: Michel Tourn
> Attachments: buildallcontribs.patch, nightlystreaming.patch
>
>
> hadoopStreaming was originally built and tested separately.
> It makes sense to keep building the hadoopStreaming code as a separate jar
> file:
> this is all client code that can be uploaded in the Job jar.
> this allows quick turnaround on production clusters
> (hadoopStreaming code updates do not require to bring down the MapReduce
> system.
> If necessary users can use their own modified versions of the hadoopStreaming
> jar but still run on the production cluster.)
> On the other hand it makes sense to build this code nightly.
> Many recent changes broke either compilation or correctness.
> All the problems would have been caught if the hadoopStreaming compilation
> and tests were run nighlty.
> Conclusion:
> the updated top-level build.xml adds the following dependencies:
> 1. Target compile calls target compile in contrib/streaming/build.xml
> 2. Target test calls target test in contrib/streaming/build.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
