Amen brother! Sharing jars between web apps is just a Bad Idea (tm).
Disk is cheap, and so is the time required to copy a jar. ...unless you are an ISP with 1000+ web apps running on a sinlge box, then it *might* be OK, but even then, I would stop and think very carefully before doing it. Larry On 6/14/05, Tim Funk <[EMAIL PROTECTED]> wrote: > Never. I share jars. I wish I hadn't. > > When you upgrade JSTL, struts, etc - all get the upgrade for free - but that > means ultra stable apps which haven't been touched in years may "magically > break". > > [Exception - log4j ... I like have a common/lib log4j] > > -Tim > > Charl Gerber wrote: > > > When do you share jars (struts, log4j, jstl, etc) for > > webapps in the common/lib directory and when does each > > app need its own "copy" of the jars? > > > > Log4j we've found by trail and error is better to have > > a jar per webapp, as the loggers seems to overwrite > > each other, but which commonly used jars (struts, > > jstl) can be shared? > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
