Steve: Currently we keep the libs required for any given module in that module's "lib" directory. As a number of things use commons logging, the jar is all over the place. There's no duplication in a deployed application, though.
We're also working towards using a common Maven repository that will eliminate the need for individual lib directories in the modules, and we've also just made the jump to "versioned" jar names, another step in the Maven direction. So in other words, there are dups now for exediency, and the way we're doing things will change soon such that there are no dups. Mike On Sat, 23 Aug 2003 08:42:26 -0500 Stephen Davidson <[EMAIL PROTECTED]> wrote: > Hey guys. > > Any particular reason that a deployed default installation of Keel has 16 copies of > commons-logging.jar, over 4 projects? > > I am a little concerned about Class/Classpath conflicts, as well as maintenance > issues. > > If a jar is already located in keel-core, keel-server, or keel-build, is it possible > for the other projects to load and use those versions? (Unless there is a > particular reason to use a local version - although in that case > an arguement can be made to upgrade the version in keel-core, etc). > > > Regards, > Steve > -- > Java/J2EE Developer/Integrator > Co-Chair, Dallas/FortWorth J2EE Sig > 214-724-7741 > > > http://keelframework.org/documentation > Keelgroup mailing list > [EMAIL PROTECTED] > http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com Michael Nash JGlobal Ltd. http://www.jglobalonline.com http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
