-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark,
On 2/27/12 9:45 AM, Mark Thomas wrote: > It could be done easily on the merge but I'd be strongly against > it. There are lots of rules for merging web fragments and I don't > think we should be logging very decision that gets made. If there's a place where the webapp is definitely set to <distributable> but then it gets un-set, that could be captured in a single place, and logged, right? Certainly, I wouldn't suggest that all the merging code be audited for this kind of thing and explicit checks added. Is there a class that represents the configuration of the webapp before it becomes an instance of a Context (or even the Context itself) that could be rigged to detect this state-change in one single location? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9LvBEACgkQ9CaO5/Lv0PBM8ACfdQAK4QS416z+pXuVzewdnZbz EhYAn2sEC8sh7nbVfnlRkm5q085ACLpm =ZY+h -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org