It does bring up a good point, one that Arjen also mentioned wrt to any API that we may layer on top on the REST API, we might want to distinguish between classes that are part of an API that we consider fully public and supported.   Regarding the REST API his suggestion was not to publish the artifact in mvn central (as it ships with the pre-build shell), it doesn't seem like we could do that in this case.