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

Doug Cutting commented on HADOOP-356:
-------------------------------------

I think this is a good idea, but I think it should be more structured.  We 
should rename the "compile" and "test" targets to be "compile-core" and 
"test-core", then add new targets named "compile" and "test" that depend on 
both the "-core" targets and the "-contrib" targets.  Thus the "compile" target 
will compile both core and contrib code, and the "test" target will test both 
core and contrib code.  Does that make sense?  That's the way we've done this 
in Lucene and Nutch.

> Build and test hadoopStreaming nightly
> --------------------------------------
>
>          Key: HADOOP-356
>          URL: http://issues.apache.org/jira/browse/HADOOP-356
>      Project: Hadoop
>         Type: Improvement

>     Reporter: Michel Tourn
>  Attachments: 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