On Wed, 2003-12-17 at 13:55, Christian Bauer wrote: > For my own projects, I name my JARs like that. The only reason we are > not doing it for Hibernate is, as far as I know: > > - CVS sucks > > - its faster to "overwrite" a file, because you don't have to change > your classpath settings in your tools (IDE)
Good points. But I think they are outweighed by the advantages of explicit naming: - You know where you are when you download the same jar from two different projects For example, if I use some Jakarta Commons stuff in my project and I download Hibernate, how do I decide which copy of commons-lang to use? I for one would be happy to reconfigure my IDE each time. +1 for explicit version naming. Regards, Bill Horsman ------------------------------------------------------- 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_id=1278&alloc_id=3371&op=click _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
