Help

The Hibernate team is proud to announce the release of 3.6.0.Final. Lot of stuff has been going on.

This is the first release from our new digs on GitHub.

We've been helping out Stale Pedersen with his work to get JBoss Application Server running on the SPECjEnterprise2010 benchmark (and their interesting interpretations of the JPA spec). Likewise, Scott Marlow and Shelley McGowan have been putting a lot of effort into testing JavaEE compatibility of JBoss Application Server running Hibernate as the JPA provider. JBoss Application Server with Hibernate 3.6 as its persistence provider is is passing all persistence related tests in both of those efforts! Great work by everyone involved.

The highlights for 3.6 include:

  • Dropping support for JDK 1.4
  • Merging of hibernate-jmx and hibernate-annotations modules into hibernate-core. For those of you using Maven, that means hibernate-core-3.6.0.Final.jar contains annotation and jmx support.
  • Improved Type support (HHH-5138 and related issues)
  • Change in DTD hosting (HHH-5485)
  • Slew of documentation changes, including introducing a new Getting Started Guide
  • Several improvements to annotations support for discriminators, column-level read/write expressions, and timestamp versions.
  • New Envers feature (ValidityAuditStrategy) as an alternative way to write history entries. See Adam's blog entries here and here for more information.

See http://hibernate.org/issuetracker for details on reporting issues. See http://hibernate.org/community for details on getting community help on usage questions.

Be sure to keep an eye on 4.0 development. No dates yet, but in 2 weeks as things settle down we will discuss the 4.0 time lines. I think we will keep the 2 week time-boxes for the Alphas and Betas as that seems like its been productive.

36 comments:
 
14. Oct 2010, 04:05 CET | Link

Oh boy. Just realized I inadvertently bundled the whole git repo into the SourceForge release bundles. Sorry. I guess the Maven assembly plugin does not exclude them by default like it does the other SCM meta files/directories. I will get the script updated.

ReplyQuote
 
14. Oct 2010, 09:30 CET | Link
surya

good

 
14. Oct 2010, 10:40 CET | Link

Didn't you use the '-e <exportDir>' option of the tagRelease.sh script? This should have 'exported' your tag without the whole .git directory into a clean directory.

 
14. Oct 2010, 11:39 CET | Link
reivax

The changelog file doesn't contain the changes between CR2 and final release.

14. Oct 2010, 14:38 CET | Link

Congrats!

When will the Maven artifacts be avail on https://repository.jboss.org/nexus ? Tnx

 
14. Oct 2010, 15:05 CET | Link

They already are: https://repository.jboss.org/nexus/content/repositories/public/org/hibernate/hibernate-parent/3.6.0.Final/

14. Oct 2010, 15:21 CET | Link
Beppe Catanese | gcatanese(AT)yahoo.com

Tnx... sorry, just asking because I couldnt find it searching the Nexus repository (indexing is delayed?)

BTW shouldnt be 3.6.0-Final instead?

 
14. Oct 2010, 16:56 CET | Link

Any chance of getting this release uploaded to Maven Central repository? For projects like AppFuse (that generate other projects), I'd rather not have to specify the JBoss repository in POMs. If I do, Maven will check JBoss for all artifacts instead of Central.

14. Oct 2010, 19:13 CET | Link
Beppe Catanese wrote on Oct 14, 2010 09:21:
BTW shouldnt be 3.6.0-Final instead?

No,

x.y.z.qualifier
is the correct format.

 
14. Oct 2010, 19:16 CET | Link

Well the correct solution is to synchronize them between. But well JBoss/Red Hat and Sonatype have been arguing about, err, I mean discussing, that for almost 2 years now. For my part I will not publish them to Central.

You can set up the order in which you want repositories searched I am pretty sure.

14. Oct 2010, 20:46 CET | Link
Pascal Thivent | pascal(AT)thivent.name
Steve Ebersole wrote on Oct 14, 2010 13:13:
No,
x.y.z.qualifier
is the correct format.

Well, maybe this is the correct format according to the JBoss conventions, but it isn't for Maven. The Maven format is

<major version>.<minor version>.<incremental version>-<qualifier>
and not following it breaks Maven's version comparison algorithm (in particular version ranges resolution).

 
14. Oct 2010, 20:51 CET | Link
Pascal Thivent | pascal(AT)thivent.name

Anyway, congratulations for this release and all the new stuff!

 
15. Oct 2010, 01:52 CET | Link

This is great, but are there any plans to release official OSGi bundles for Hibernate?

 
16. Oct 2010, 02:36 CET | Link

We are looking at that for 4. Bundles themselves are not the issue, though; the issue is classloading, which we do a lot of. I think I accounted for this in 4 with the notion of classloading as a service for which the environment can plug in different behavior. If its important to you perhaps you can take a peek?

16. Oct 2010, 02:41 CET | Link
Pascal Thivent wrote on Oct 14, 2010 14:46:
Steve Ebersole wrote on Oct 14, 2010 13:13:
No,
x.y.z.qualifier
is the correct format.
Well, maybe this is the correct format according to the JBoss conventions, but it isn't for Maven. The Maven format is
<major version>.<minor version>.<incremental version>-<qualifier>
and not following it breaks Maven's version comparison algorithm (in particular version ranges resolution).

I thought Maven were moving to support osgi-style versioning (?) which the JBoss convention follows...

Anyway, I understand frustration over a particular something not working, but considering the Maven developers themselves repeatedly tell us to not use version ranges for defining dependencies I have to say that interop with OSGI is more important here, IMO.

 
16. Oct 2010, 13:26 CET | Link
masotime

For those who might be interested, here is a set of working Maven pom.xml Entries to get Hibernate 3.6.0.Final into your project.

Under <repositories>

    <repository>
      <id>JBoss</id>
      <name>JBoss repository</name>
      <url>https://repository.jboss.org/nexus/content/groups/public-jboss</url>
    </repository>  

Under <dependencies>

    <dependency>
      <groupId>org.hibernate</groupId> 
      <artifactId>hibernate-core</artifactId> 
      <version>3.6.0.Final</version> 
    </dependency>

The path suggested earlier https://repository.jboss.org/nexus/content/repositories/public/org/hibernate/hibernate-parent/3.6.0.Final/ does NOT work. The repository https://repository.jboss.org/nexus/content/repositories/public/ is fine, but the artifact is hibernate-core, NOT hibernate-parent. I went around in circles with Missing artifact org.hibernate:hibernate-parent:jar:3.6.0.Final:compile errors before realizing this.

 
18. Oct 2010, 18:36 CET | Link
Cage
Thank you very much, had spent about an hour figuring this out.
 
19. Oct 2010, 05:31 CET | Link
<blockquote>
_Steve Ebersole wrote on Oct 13, 2010 22:05:_<br/>

Oh boy. Just realized I inadvertently bundled the whole git repo into the SourceForge release bundles. Sorry. I guess the Maven assembly plugin does not exclude them by default like it does the other SCM meta files/directories. I will get the script updated.
</blockquote>

Click HELP for text formatting instructions. Then edit this text and check the preview.
 
20. Oct 2010, 18:17 CET | Link
Pierce T. Wetter | pierce(AT)paceap.com

I get that there is a change to the type system because I've read the issues you link to about 3 times now.

What I don't get is what the benefits to me as a Hibernate user are from the changes to the type sytem.

 
24. Oct 2010, 15:01 CET | Link

Can someone please throw some light for Building Hibernate From Src 3.6 and Importing it into IDE in the wiki?

I am able to build the new source using Gradle, which I checked out from Git. But eclipse project import is not working for me. I ran the gradle :eclipse command, and the entire hibernate-core was successfully imported in Eclipse too, but as a folder, with subfolders for each of them (c3p0, cache, etc..) with no build path set, instead of standard Java Project.(Is this the way it normally happens or I have messed up?) In fact, no .project and .classpath files were generated I guess I am missing something...

 
24. Oct 2010, 15:52 CET | Link
KCore wrote on Oct 24, 2010 09:01:
Can someone please throw some light for Building Hibernate From Src 3.6 and Importing it into IDE in the wiki? I am able to build the new source using Gradle, which I checked out from Git. But eclipse project import is not working for me. I ran the gradle :eclipse command, and the entire hibernate-core was successfully imported in Eclipse too, but as a folder, with subfolders for each of them (c3p0, cache, etc..) with no build path set, instead of standard Java Project.(Is this the way it normally happens or I have messed up?) In fact, no .project and .classpath files were generated I guess I am missing something...

Only the master branch is using Gradle for builds...

 
25. Oct 2010, 07:38 CET | Link
KCore

Steve, sorry if I am ignorant. Are you saying that I should build using maven? If that is the case, then I cannot find the pom.xml for hibernate-core.The pom.xml that are present include the hibernate-tutorials, cache, reference manual, etc. Should I download the source from SourceForge and then try?

 
26. Oct 2010, 13:26 CET | Link
Jukka Nikki
Thanks for new release. I had problem with getting JPA 2.0 API:s from maven repository. I wonder if this is right place. Some caching system or other was blocking my access so that this was only POM I managed to reach.

property

<hibernate-jpa-2.0-api-version>1.0.0.Final</hibernate-jpa-2.0-api-version>

dependency

<dependency>
   <groupId>org.hibernate.javax.persistence</groupId>
   <artifactId>hibernate-jpa-2.0-api</artifactId>
    <version>${hibernate-jpa-2.0-api-version}</version>
</dependency>

repository

<repository>
    <id>JBoss maven2</id>
    <name>JBoss maven2</name>
    <url>http://repository.jboss.org/maven2</url>
</repository>
 
27. Oct 2010, 16:08 CET | Link
KCore wrote on Oct 25, 2010 01:38:
Steve, sorry if I am ignorant. Are you saying that I should build using maven? If that is the case, then I cannot find the pom.xml for hibernate-core.The pom.xml that are present include the hibernate-tutorials, cache, reference manual, etc. Should I download the source from SourceForge and then try?

If you want to build the 3.5 or 3.6 branches, use Maven. If you want to build master, use Gradle. Not sure how much more clear I can make it :)

 
27. Oct 2010, 16:10 CET | Link
Jukka Nikki wrote on Oct 26, 2010 07:26:
...

You must name the JBoss repository in the first place to get the Hibernate artifacts; so not understanding why you needed to do this again...

 
05. Nov 2010, 08:46 CET | Link
I want to download.
 
05. Nov 2010, 09:22 CET | Link

please tell me how to download the Hibernate Core 3.6.0.Final Release jars or send it to my email loveluomeng@yahoo.com.cn, it is hard to find the download links.

10. Nov 2010, 08:51 CET | Link
Beppe Catanese wrote on Oct 14, 2010 08:38:
Congrats! When will the Maven artifacts be avail on https://repository.jboss.org/nexus ? Tnx

Click HELP for text formatting instructions. Then edit this text and check the preview.

11. Nov 2010, 20:51 CET | Link

Excelent !!!. . . . Downloading. . .

 
21. Nov 2010, 06:20 CET | Link

please tell me how to download the Hibernate Core 3.6.0.Final Release jars or send it to my email zhiquanliu@foxmail.com, it is hard to find the download links.

thank you!

 
21. Nov 2010, 11:25 CET | Link

I need get it!

 
22. Nov 2010, 14:11 CET | Link
wang_q_d | 824185601(AT)qq.com

Click HELP for text formatting instructions. Then edit this text and check the preview.

 
27. Nov 2010, 13:38 CET | Link

I need a annotation API.

 
29. Nov 2010, 14:20 CET | Link

I need to get it.Thank you!

14. Jan 2011, 21:41 CET | Link

Maven2 still has severe problems with anything other than 2 part or 3 part versions (with or without the -qualifier), especially when specifying version ranges (OSGI typically does this for dependencies). Maven3 (released Oct 2010) for the most part fixes this problem. See http://docs.codehaus.org/display/MAVEN/Versioning. However many of us are still on maven2 because the API changes or the site documentation changes require a full project migration.

 
31. Jul 2014, 02:38 CET | Link
jack

Rapid Content Wizard Lightning is a best quality Air Conditioning Repair North Palm Beach content creation software that will help you to Instantly create unlimited, unique, high-quality Site content on autopilot with Just the click of a mouse

Post Comment