Rename tasks/warbler.rb -> tasks/jar.rb
MeerkatEnvironment can bootstrap an arbitrary modern jruby.

We'll use it to not depend on HBase's old pinned version.
Don't need curator anymore.
Walk away from jrubyc.

It's unnecessary, given that we're authoring our own environment loader.
Walk away from warbler.

Meerkat *apps* will probably use it (and we'll demonstrate an example app in spec/integration soon), but meerkat itself is now simply a gem.
Include classes/ in built gem.
Move hbase env var magic into spec_helpers/hbase.rb.

Also don't try to require the meerkat jar; doesn't exist!
tweak
Begin building an example app and accompanying acceptance test suite.
The example app mrproper tasks wipes all uncommitted state.
Move to modern jruby, bring warbler in to example app.
Warbler is still getting aggro over gem paths..
Use a local gem repo to capture example app deps.

Also, annoyingly, I've just noticed that 'meerkat' is the name of an existing gem.
No need to require meerkat/version.

Just wanted to prove the gem would resolve.
Don't need this load path tweak.
Call our gem meerkatx for now.
Bring jbundler and rake into the example app.
Make a failing test.

The example app can jar itself, now we need to prove that our compiled class files can get in there.

Note this test is a not a demand for correctness from the library.  Rather it documents how the library expects to be used.
Meerkat::Packaging contains utilities to ease client app packaging.
Make the test pass.