Hi, Simply overlaying wars is the first step of handling war dependencies, but it doesn't work for more complex systems. For example: If you have an application context file in the same location in all the wars, they simply replace each other when they are overlayed, which destroys the application. I have a solution to this problem (which I made in a process resources plugin for Maven 2) which is:
Take the parts of the war file that normally would go into a jar file and put them into a jar file. Overlay the rest. In detail this means, take the contents of WEB-INF/classes and the complete META-INF directory and zip these into a jar which is placed in the target project's WEB-INF/lib. The remaining files, which are only web resources, taglibs etc, can be overlayed as usual. The web.xml you might want to just ignore. In this case, alle the application context files are placed in its own jar file together with all the other jar files, making the war projects look like regular jar projects in the final war. Does this sound like something? If you like, I can put a suitable licence on my plugin and make it available somewhere. Regards, Torgeir --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
