> what's wrong with using the manifest? A few things spring to mind: 1. You have to open the .jar and extract/view the manifest to find out the version. If the version is in the filename you can simply see what the version is.
2. Not all library .jars include the version in the manifest. This means that the hibernate project would have to modify the content of those library .jars. Renaming the .jar seems less intrusive. 3. It also doesn't solve the library version history in cvs issue very well, because even though you can now see the history on the file, you have to get each revision individually to open it and view the manifiest to figure out the versions. A way around that would be to rely on commiter's to add the version in the cvs comment or tag each revision with the library version. But this is bad due to the normal reasons why duplication is generally bad in software development. brad ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
