Grab a version and STICK with it

Aren't we REALLY in great need to resolve the version/revision issues in java. Ever tried to use e.g. Hibernate with another Open-Source product? Ever praised for the two products to have compatible dependent library versions? I have... And it SUCKS that I have to.. I think we really do need some way of versioning either the class files or the JAR library files, and ofcoz this has to extend to the classloading mechanism aswell. Ohh yes, I started out wanting to bile the commons-* "I-depend-on-just-about-all-other-commons-packages- but-I-thought-it-would-be-funny-NOT-to-pack-it-all-in-one-jar" dependency model, but decided not to - and WHY ohh god WHY are soooo many OS products using the commons-logging crap.. I mean - for the love of god - I can't imagine a single valid reason for using it..

Update: Is it just me or do we also need an extra scope definition for e.g. methods? I mean - wouldn't it be nice if we had a "archive" scope which was much like the "package" scope, but for classes in same archive (JAR) .