Almost definitely due to a switch to Maven as the build system. It automatically includes the version number.
As to why they include the version number, it just makes sense. One complaint I have with hibernate is that it ships with the version number removed from the files and I have to goto a little bit more effort to work out if I have classpath clashes. Hen On Wed, 5 May 2004, Glanville, Jay wrote: > Hello All. Silly (or insignificant) question time. > > Back in January for Collections 3.0, the deployed binary jar file had > it's filename changed to include it's version number. (e.g.: > commons-collection-3.0.jar) > > What was the reasons for this change? > > I believe I know the answers to this question, but my co-worker needs to > hear it from the source. > > Thanks. > > -- > Jay Glanville > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
