RE: [Springframework-developer] JARs .. can they be named based on their version ?

[Ou, R. <Ro...@sa...>]

+1
=20
We do this for our project...
=20
Rong

-----Original Message-----
From: spr...@li... =
[mailto:spr...@li...]On Behalf =
Of Cameron Braid
Sent: Tuesday, March 23, 2004 9:22 PM
To: spr...@li...
Subject: [Springframework-developer] JARs .. can they be named based on =
their version ?


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