-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mike,
On 1/14/2010 6:45 PM, youngm wrote: > * It would seem that the change tracking of a process like that above would > be very difficult. It would be hard to answer questions like "What patches > have I applied to these 20 applications in production?" If there were > simply a folder with the patches right there then it becomes very easier to > see how this running application's configuration differs from the > configuration the archive was built with. This becomes more and more > important the older an application gets and the more patches applied to it. I would think that going through a complete release cycle with the patch would be /more/ trackable than just tossing a bunch of new JAR files into a directory. You would also get the benefit of /testing/ the patch instead of just crossing your fingers and doing a blind update on a production machine. But that's just me. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktQiZMACgkQ9CaO5/Lv0PCBdgCgmODUCBeM79Be4RJ+YueZ3POV dRYAoMBoNxITMINeWQcfRGDr/GRS0H/A =GKvr -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
