Publish to Maven Central [help offered]

[GoogleCodeExporter]

Reason: It'd be nice to use dirty-mockito a bit more widely, but adding a 
repository that can disappear is often not allowed on significant open source 
and commercial projects.

I recently jumped through this hoop, and it wasn't as challenging as I'd 
feared.  Sonatype were very quick in setting up the staging repository and it 
just took me a few iterations to pass the quality checks (i.e. that I was 
providing sources, and javadoc).

If you'd like some help, then I'd be happy to oblige.

Original issue reported on code.google.com by nea...@gmail.com on 21 Jun 2011 at 10:55

[GoogleCodeExporter]

You might also consider joining JUnit over on github, as it's a lot easier to 
fork and merge patches over there.  It's no problem to keep the full SVN 
history too.

Original comment by nea...@gmail.com on 21 Jun 2011 at 10:57