Cameron,
What's stopping you from renaming them yourself, and deploying that way?
This is what I do personally in some projects that use Spring.
Everything has a version number, whether it shipped that way or not.
I realize we could do it too in Spring out of the gate, but there's pros
and cons to both sides though...
Regards,
Colin
Cameron Braid wrote:
> 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.
|
