OK I'll leave it in common/lib. The problem with WEB-INF/lib is that is takes too much time to update all webapps. We have a rather cumbersome environment. Each app has to go through four environments (development, integration, certification, production) before it is available to the customer. Hopping from one environment to the next can take up to two days each because after Sarbanes-Oxley all we developers have access to is development and that's it. Now imagine I have 30 apps using this jar. If I need to make a change to the jar it becomes a nightmare to deploy.
Thanks for the help tho =) -----Original Message----- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, June 11, 2004 9:56 AM To: Tomcat Users List Subject: RE: Common/lib works shared/lib doesn't Hi, It's OK to leave it in common/lib. (IMHO it's also fine to have a copy for each webapp in WEB-INF/lib, but you stated you don't want that). Yoav Shapira Millennium Research Informatics ********************************************************************** The content of this e-mail message and any attachments are confidential and may be legally privileged, intended solely for the addressee. If you are not the intended recipient, be advised that any use, dissemination, distribution, or copying of this e-mail is strictly prohibited. If you receive this message in error, please notify the sender immediately by reply email and destroy the message and its attachments. ********************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
