Hibernate 3.1.2 has just been released: http://sourceforge.net/project/showfiles.php?group_id=40712&package_id=127784&release_id=388971

This release fixes, amongst other minor bugs/enhancements, bugs with Session closure checking, some potential bugs in HQL parameter binding, and issues with "borrowed connections" (i.e. Session.connection()) with agressive connection releasing.

Hey there,

The ibiblio maven repository for Hibernate is a bit out of date. The most recent version there is 3.1rc2. Could some kind soul from Hibernate central please bring them up to date?

how did u solve the problem with hibernate new releases and maven?

Yeah, I noticed the same thing when I tried to have my maven script pull the new version.

Steve - can we get an update out there?

Thanks,
Lou

Sigh...

I guess I get to discuss this every release?

In order to upload to maven's repo, they require a project descriptor. As Hibernate does not use maven for building, we do not have this descriptor. And I am not inclined to maintain such a thing.

What's the reasoning behind that??

If enough of us are asking for a maven distro why wouldn't you accommodate that?

It was being put out there before up to 3.1RC2...what happened?

Isn't "we don't use maven, so we don't have a project descriptor available nor testable" enough ?



apparently noone cares enough to do it, not even people from the maven community.



we never put it up there because we don't like to distribute things we dont/cant verify.

All,

I'm using hibernate-3.12 from http://www.ibiblio.org/maven2/org/hiber ... -3.1.2.jar but the http://www.ibiblio.org/maven2/org/hiber ... -3.1.2.pom
is using a wrong version of commons-collection (version 2.1.1) generating a "java.lang.NoClassDefFoundError: org/apache/commons/collections/ReferenceMap" in projects that doesn't depends on commons-collections.

As a work around I declared a fake dependency in my pom.xml to commons-collections 3.1 (latest stable release).

I dont know if it's here the right place to post this. I hope that someone could update the depedency of commons-collections in hibernate-3.1.2.pom to a version that has org.apache.commons.collections.ReferenceMap. If this isn't the right place to post, please, let me know.

Thanks,
Jonas

Would you guys ever consider switching to building with Maven? I've personally used both extensively, and I can see no reason why you would use ant over maven.

On the ibiblio verification topic, doesn't the fact that thousands of developers trust it enough to use it answer the question? Verification should be more of a concern for the end user, and clearly end users are satisfied with their level of assurance from ibiblio. I get the sense there's some religious feeling over there on this issue, which should raise a red flag in and of itself. It just ends up being a pain in the a#($ for the many people like me who would prefer to access the jar on ibiblio.

I'd bite the bullett and switch to maven now instead of 2 years from now when it's even more painfully obvious that it's a better build system. I'd even volunteer to write the project.xml. Just my overly honest 2 cents.

maven1 never got close to be seriously considered over a simple ant file.
...and no, maven is not obviously a better build system

maven2 is (maybe) another story, but we don't just switch because its cool/hot; it should solve a problem or be better(tm).

Why should we switch if what we have now works ?

Verification topic - just because thousands of developers trust it, none of those "thousands" have stepped up and done the actual work of maintaining the pom and verifying that the specific hibernate pom works.

..personally I don't find ibiblio interesting before it also contains src/docs/etc of the jars (that might have changed recently, but i definitly were not the case before)

the groupid is renamed from hibernate to org.hibernate . This should contain a 3.1 version.