This is now the de facto standard for releasing jar files in the OSS
projects I'm involved with, mainly due to maven and overall
clarity/convenience.
Stephen
- Original Message -
From: "Glanville, Jay" <[EMAIL PROTECTED]>
Hello All. Silly (or insignificant) question time.
Back in Januar
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 li
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,
