committing 2.0.0 release tagged poms
Whoops -- Somehow I did the 'merge mr, run maven release plugin steps' in the wrong order. So we have a tag (with the correct code...even the poms) for 2.0.0 in tags, but it left master at 2.0.0-SNAPSHOT. The tag is correct, as well as the maven artifacts. Only master was left in the wrong state, version wise.
This just turns in the poms with the 2.0.0 release version.