All:

I've created a fork of mrunit from Hadoop's contrib directory at
https://github.com/esammer/mrunit

Why:

* MRUnit could benefit from a separate development and release cycle than
that of Hadoop itself. This would allow MRUnit to evolve independently of
Hadoop.
* Moving projects out of contrib simplify Hadoop's build and the artifacts
that need to be maintained.
* I've heard rumblings that contrib is generally frowned upon by some of the
committers. I agree.

What is already done:

* Build system ported to Maven.
* No more build warnings re: generics or deprecation.

I think it makes sense to remove mrunit from contrib (after a deprecation
period) but I'm curious to hear others' opinions. If the community at large
decides it makes sense to retain mrunit in contrib I'm happy to provide
contributions back. I'd also like to offer commit status on the fork to any
current Hadoop committers who are interested. The project is being hosted on
Github to ease collaboration. Pull requests are greatly appreciated.

Regards.
--
Eric Sammer
twitter: esammer
data: www.cloudera.com

>
> I think it makes sense to remove mrunit from contrib (after a
> deprecation period) but I'm curious to hear others' opinions.
Oh please do take things out of contrib. I'd love to see all of it move to
Github. Thanks for putting in the time for MRUnit.

+1.  I just started a thread on moving all components out of contrib.

nige

On Jan 30, 2011, at 6:50 PM, Jeff Hammerbacher wrote:

>>
>> I think it makes sense to remove mrunit from contrib (after a
>> deprecation period) but I'm curious to hear others' opinions.
>
>
> Oh please do take things out of contrib. I'd love to see all of it move to
> Github. Thanks for putting in the time for MRUnit.

On Jan 30, 2011, at 7:59 PM, Nigel Daley wrote:

> +1.  I just started a thread on moving all components out of contrib.
Pushing them randomly to the web 2.0 version of Sourceforge (where they will never be seen from again) doesn't sound like a decent, long term strategy.

+1 - thanks for taking the initiative to clean this up!

You should file a JIRA with a patch that removes src/contrib/mrunit and
removes it from src/contrib/build.xml.

- Aaron
On Sun, Jan 30, 2011 at 7:59 PM, Nigel Daley <[EMAIL PROTECTED]> wrote:

> +1.  I just started a thread on moving all components out of contrib.
>
> nige
>
> On Jan 30, 2011, at 6:50 PM, Jeff Hammerbacher wrote:
>
> >>
> >> I think it makes sense to remove mrunit from contrib (after a
> >> deprecation period) but I'm curious to hear others' opinions.
> >
> >
> > Oh please do take things out of contrib. I'd love to see all of it move
> to
> > Github. Thanks for putting in the time for MRUnit.
>
>