On Fri, 14 Mar 2003 [EMAIL PROTECTED] wrote:
> Right, now for my question : The dependancies for many projets are > pretty much the same, projets come with the jars they depend on > (and some do not) which makes for a lot of duplication. Is there a quick > way around this, a quick way to avoid duplication? Should a standard be > set to avoid such duplication? Or is this duplication justified? A quick [though ultimately painful] way around it is to stick things into a shared classpath directory. With Java you can put things in your JRE/JDK's lib/ext directory, with tomcat there is a common/lib directory that serves much the same purpose for most things. The problem here comes with the clash in versions, which is why duplication is justified. One piece of code might need log4j 1.1.7 and might not work on 1.2.3 [i'm making up version numbers, but they're closeish], while the rest might happily upgrade to that version. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
