Publish all artifacts to Maven Central

[ctubbsii]

Currently, only the ri/ module has been updated to publish to Maven Central. The rest of the multi-module project should be similarly updated.

Note: I'm creating this issue as a tracking/discussion issue. I intend to work on a pull request which does this soon, unless there's a reason to not do it.

[amaembo]

I don't know whether other artifacts are useful for somebody. If you think they are, then go ahead. Though probably it would be easier for you just to fork the project and request your own group ID in Sonatype (unrelated to findbugs) and publish artifacts there...

[ctubbsii]

Splitting up the project would be to the detriment of its users, I think. It would only worsen the confusion caused after the transition from code.google.com. I'm not sure if anybody cares about the other artifacts, but I'll consider making a pull request when I get a chance, just in case. It can't hurt to release them to Maven Central, in any case.

If you're not interested in managing pull requests for the other parts of the code, and the findbugs project isn't willing to host/maintain the project (findbugsproject/findbugs#136), then we could also move or fork the project to the code.revelc.net organization (https://github.com/revelc), and release from there. That's a little GitHub organization I created to help host random open-source projects and give them a canonical upstream community where they can be nurtured.