This is still missing some stuff but I wanted to get feedback on if this was useful / interesting before sinking more time into it.

Typical gradle subproject structure plus:

- Multi-release jar for shims subproject
- Move examples into typical `src/main/java` and set up tasks for each one, removing the need for a separate shell script
- Move JMH benchmarks from `src/main/java` to `src/jmh/java` since that's how the JMH plugin prefers it. (This allows benchmarks to live in the same module as the normal code, if desired.)

Missing things:

- Deploying releases (use Bintray to avoid Sonatype Nexus pain?)
- jxr
- perhaps other subtleties I missed/forgot

For the moment publishing only works to maven local.

…APSHOT'.

This makes it possible to have the generated artifact have an artifact
id of RoaringBitmap *and* have inter-subproject dependencies be
consistent with the generated pom without doing any xml wrangling on
the generated poms.

(Attempt #2 -- first one dropped some test binary inpputs)

…APSHOT'.

…NAPSHOT'.

I guess that this is needed to keep things in sync.

Updating instructions...