Worked through a number of issues with doing "project per module" cleanly, but came upon what may be a show stopper: Each module ends up with its own .project and .settings/, and (unless there is a trick that I'm missing) there isn't inheritance going on here amongst the projects. What that means is that you can't set up something like the code templates for Rice in just the root project – instead you have to painfully repeat the configuration for each module. We could try to propagate these settings during the build, but that would put us back into ungainly hack territory.
Someone mentioned that a new version of the m2eclipse plugin just came out so I'm going to try to download that next and see if it magically solves this problem. After that though, I'm pretty much stuck with trying "mulitple Maven modules mapped to a single Eclipse workspace project" which I've heard has has the major downside of unrealistic classpathing (everything munged together).
I'm open to any and all super-awesome suggestions on this.