benoitx wrote:
<feelFreeToDismiss>
As an aside, I'd prefer if Hibernate was using jar names with versions... e.g. hibernate-3.1.3.jar
I know it was dismissed before on the ground of being easier to just replace the hibernate3.jar with the latest one... but I prefer explicit changes to "latest" and unclear jars....
</feelFreeToDismiss>
Here here... library version management it always best done with a unique name per version. Just take a look at windows DLL mess to understand why, even they use soname like versioned filenames now with DotNET.
But its no problem to rename it before use, I always do.
It would also be good practice to see all the JARs in the lib/ directory of the distribution to follow suit. It just makes version management so much simpler and understand for everyone.
The only bad point is the possibility of duplicate JARs of different versions getting into the classpath, but this problem is so easy to spot its really a non-issue, than the opposite problem of having to dig into every jar to verify its version when you have a versioning concern. This becomes a waste on everyones time and so easy to fix at source.
YMMV