> On Tue, 2011-04-26 at 09:46 -0500, David M. Lloyd wrote: >> It shouldn't be a global setting at all. It should be per-deployment >> and it should default to "on" when there is exploded content and "off" >> otherwise. In other words: the user should never even need to know >> about it. > > Ok, since I strongly disagree, I'll let you make that change. I also disagree, but for different reasons. Whether or not you run in development mode should not depend on exploded/unexploded.

Some tools used in development would deploy unexploded. Development mode is used for more than just hot deploy of JSP and Facelets. It also determines what kind of error messages you see in the browser. So even if a developer isn't interested in JSP/Facelets hot deploy he would certainly want to see the error detail that development mode provides in the browser.

I think we simply need to decide if the default configuration for the community edition will be to set things to development mode the way we have traditionally done. I am in favor of that, at least for standalone.