Yes, I meant multiple maven modules. I think ideally, there'd be a maven module with the POJOs and resources and stuff (the "library"; technically, this could be server-base), and then a separate module for each supported service (embedded jetty launcher, war packaging, tomcat-specific support).
When I say "I just don't know that we need... right now...", I'm mainly expressing my dislike of the monitor being part of the core project (as well as the fact that we haven't really discussed multiple modules in terms of the future of the monitor). I think that I'd much rather prefer all the monitor be a client-only service which simply talks to Accumulo's metrics API and displays it conveniently. That way, we can separate out the service as a truly separate thing (modules and all), but which could also just as easily be swapped out for another monitoring service, if desired. Until things get to that point, I think I'd rather just stick with a single, convenient module which launches the service in one way (embedded Jetty). Maybe it could also build a generic WAR package for deployment in a separate container, but I wouldn't want to see a lot of heavyweight refactoring support for the monitor as it exists in the core project. I'd rather see work to make it replaceable and moved to its own contrib repo, with support for additional containers supported in separate modules there.
However, I place emphasis on the "don't know" part of my comment, because I think additional thought needs to be put into this (including reviewing on my part of patches/contributions).