The soon-to-be-attached patch lets you work on Avro from within Eclipse, if that's your style.
I've added the following to the README:
To use Eclipse, use the "ant eclipse" target to trigger generating a .classpath
file, and also trigger compilation (to pull in the maven dependencies, etc.)
You must also make sure that your avro checkout directory is "avro". You
should then be able to create an Eclipse project pointed to your checkout, and
run the unit tests from Eclipse's runner.
Note that the "Eclipse Builder" is configured to compile twice: once with
Eclipse's built-in compiler, and another time with ant. Eclipse is happier
this way, though the classpath is configured to ignore Eclipse's compilation.
Everything here is incomprehensible XML boilerplate. There's a new ant target to create the .classpath file.
I'm able to run all but the interop test that requires a server from within Eclipse. I welcome other Eclipse users trying this out to see if it works.