Hibernate Annotations 3.4.0.GA
http://in.relation.to/Bloggers/HibernateSisterProjectsAlignedWithCore330

Hibernate EntityManager 3.4.0.GA
http://in.relation.to/Bloggers/HibernateSisterProjectsAlignedWithCore330

Hibernate Validator 3.1.0.CR2
http://in.relation.to/Bloggers/HibernateSisterProjectsAlignedWithCore330

Hibernate Shards 3.0.0.Beta2
Horizontal partitioning solution for Hibernate

Hibernate Search 3.0.1.GA
http://in.relation.to/9173.lace

Downloads available at http://www.hibernate.org/6.html

Is there any chance to have source JARs included in the Maven repository? I remember raising it for the last release (it was Annotations, I think), and now, none of the newly released components have sources!

Also, what's the deal with the dependencies for EM, specifically for the artifact ejb3-persistence - why is it now packaged in the Hibernate group ID, if it doesn't belong to it?? Last time I checked, this code was part of javax.persistence? Now some releases use the old dependency, some use the new one, and the app has to include both...

Thanks,

Alex

The jar sources will be included in the next releases. Someone just helped me add some ant tasks that will automatize things.

As far as ejb3-persistence it has always been part of the hibernate.org groups as far as I am concerned. When the pom was managed by the community some mistakes have been made. We are taking over the responsibility for the pom and fixing errors from the past.

Well, I could only judge by the fact that, when I was building my app using Hibernate 3.2.5, the ejb3-persistence wasn't included... maybe an exclusion was in place.

In any case, my only problem is the way the ejb3-persistence is declared. I understand that you guys are maintaining your own Maven repo, so as to get greater degree of independence from the not-so-responsive main repo team... but why a change in group ID? Why not simply declaring this 1.0.1 version under javax.persistence, and keep it in JBoss repo this way, not breaking compatibility with the 1.0.0 from the main repo? After all, a lib that only has a javax.* package, doesn't belong to org.hibernate even semantically...

Further to this, the JPA dependency for Hibernate EM 3.3.1 is indeed declared as , not as ejb3-persistence. This was clearly added in 3.3.2.

Upd: Same for Annotations - 3.3.0 is declared with javax.persistence, and 3.3.1 - with org.hibernate

Sorry, double post...

Sun owns javax.persistence so we cannot add our own stuffs in it. Especially when doing implementation previews (but that's not the only case).

As for the older version of EntityManager and Annotations, as I told, there were not managed by the hibernate team and hence had some inconsistencies I wanted to fix.

Ah, I see. Well, then my only hope would be that Seam eventually switches to the new JPA declaration, too.

Thanks for the clarification.

This will be the case, I talked to Pete about that.