[Berin Loritsch] > Thomas B. Passin wrote: > > [Elliotte Rusty Harold] > > > > > >>You're still using the classpath for jars? I only do that when I want > >>to change the classpath on a per-run basis, in which case I am > >>changing it and using the version number is not a problem. However, > >>for standard libraries like xerces.jar that are shared among multiple > >>applications I just dump them in my ext directory and forget about > >>them. It's much easier than changing the classpath. My normal > >>classpath doesn't contain any jar archives, just directories of my > >>own compiled code that hasn't been bundled into a jar. > >> > > > > If all those versions are in the ext directory, how do you make sure that > > any given app finds the right version? > > > For some jars like Xerces/Xalan, if you code to the plugable API (aka > JAXP), you only need to upgrade the jar--no recompilation or refactoring > needed. > > For others, like the Commons Logging API change recently, this approach > becomes messier.
Yes... and I'm asking about the case where different apps need different versions of the jar, but the interfaces are still the same (or isn't that a problem in practice?) Tom P --------------------------------------------------------------------- In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
