Are you using an exploded deployment? If you are, and have setup your server to reload your context on change, you shouldn’t need to restart very often
At one time I had a project which had an included Utility project. The Utility project was compiled and packaged into a JAR file, which was then placed in the /lib/ directory of the actual project. Any changes to the Utility project required a server restart (pop-up recommended server termintation).
In this scenario, re-deployment takes place every time the Utility project code is changed. Lots of mouse clicks. I often wished there was a (terminate/ re-deploy/ server start) button :-))
But yes, not a really urgent matter.