> (Moving this thread to the Turbine list...)
good idea. :-)
> Okay, I'll move it back if you want. However, I don't see how it's any more
> "global" than jndi.jar or village.jar, et. al.
those files are on my shit list next...one thing at a time. :-)
The criteria is like this:
#1. files that we do not have the source code to can live within tomcat/lib.
#2. files that are static and do not change very often(ie: village) can live
within tomcat/lib.
#3. files that we have the source code to and are not static (ie: turbine.jar)
and/or execute Class.forName() within their code should live within
/WEB-INF/lib.
there is all sorts of classloader issues that are resolved by simply putting
stuff into WEB-INF/lib/. I know it ends up being a duplication of .jar files
all over the place, but in the end, it can be easily resolved by having an
upgrade path within the newapp.sh application.
-jon
--
Scarab -
Java Servlet Based - Open Source
Bug/Issue Tracking System
<http://scarab.tigris.org/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
