Unfortunately, I'm not sure I have an easy way to add that repo to our
build system, since we use a proxy for maven resolution.  I'm not seeing an
easy way to add that repo, without it overriding everything in maven
central (which maybe is ok, but I'm not sure).

It does look like that version will work correctly, however.

Since we can be certain that the one currently in maven central doesn't
work, would it be possible to upload a patched version there?  Or at least
remove the bad one altogether from maven central?  (which would allow me to
add the apache releases repo more safely has a lower priority repo than
maven central on our proxy).

On Wed, Jul 24, 2013 at 6:01 AM, Joe Stein <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB