https://issues.apache.org/bugzilla/show_bug.cgi?id=10021
--- Comment #5 from Christopher Schultz <ch...@christopherschultz.net> 2010-12-15 11:22:30 EST --- There's also the problem of somehow merging configurations: sometimes, server.xml is updated even within a stable line. The safest thing to do is simply leave server.xml alone, but we might still run across problems there. How traumatic are changes allowed to be within a particular version line (6.0.x)? For example, the JreMemoryLeakDetectionListener was introduced at some point in 6.0.x but hasn't always been there. That's not a problem as /adding/ something isn't a big deal. Do we ever /remove/ anything that might cause a startup failure? Similarly, sometimes configuration defaults change: do we have to detect whether the old defaults are in use and then explicitly set them to their old default values in server.xml/web.xml/context.xml? The process of upgrading could seriously break someone's configuration. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
