I was reading a lot about how one of maven's best features is the dependency handling: there is no need for a directory of jar files. Everything is specified in the dependency management and the repository has the needed jars. Sounds good.
One of my coworkers raised however an issue the other day which I couldn't answer. Any ideas welcome. Here is the story: building with ant, our project had one directory with all the jar files. On our production server the contents of this dir was in the tomcat/shared library (we have several apps running on the servers and they share a lot of the dependencies). Keeping it up to date with new jars was as easy as synching with our ext_libs folder. Now, we use maven. There is no more ext libs folder. The dependencies however are not included in the wars (scope: provided). They are already in the shared lib of tomcat. Question is: how are we supposed to generate the contents of the tomcat ext libs folder at this point? Looking up 100 dependencies from several pom files and extracting the jars from the repository doesn't seem so great. It seems as with the dependency managament suddenly we lost the ease of keeping our production server shared library up to date. I wonder if there is some solution to this. Attila __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
