|
From: Cameron B. <ca...@da...> - 2004-03-24 03:22:11
|
I have run into a problem with supporting multiple applications that use different spring versions. We store all of our jars, for every application, in a repository. In eclipse we link against them, and when deploying we copy them into the war/ear. I upgraded an app to spring 1.0 HEAD yesterday, causing the new aopalliance.jar to be overwritten in our repository. I now receive an aopalliance exception because an app, using spring rc1, requres the older aopalliance.jar file. This issue would be avoided if every jar that spring uses (including the spring generated jars) are stamped with their version in the filename. I (and others) managed to convince Hibernate, WebWork2 and Xwork to follow this pattern as well. I think it is a great idea as it explicitly allows identification of changes in jars. Any thoughts ? Cameron. |