[ http://issues.apache.org/jira/browse/HADOOP-356?page=all ]

Doug Cutting resolved HADOOP-356.
---------------------------------

    Fix Version/s: 0.5.0
       Resolution: Fixed

I changed this some and committed it.  Since the old "compile" target is now 
named "compile-core", most of the dependencies on it needed to be changed to 
"compile-core" too.  Also, I renamed the "compile-test" target to be 
"compile-core-test".

I note that the contrib packages are not included in distributions (the "tar" 
target).  They probably should be.  Michel, would you like to modify "tar" to 
include the contrib code?  This should be done in a separate bug.

> 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
>             Fix For: 0.5.0
>
>         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

        

Reply via email to