Hibernate Annotations, EntityManager and Validator compatible with Core 3.3.x
by Emmanuel Bernard
The Hibernate team is pleased to announce the synchronized release of:
- Hibernate Annotations 3.4.0 CR1
- Hibernate EntityManager 3.4.0 CR1
- Hibernate Validator 3.1.0 CR1
- Hibernate Commons Annotations 3.1.0 CR1
These release primarily ensure compatibility with the new Hibernate
Core 3.3
Aside from the compatibility, noticeable work are:
- Maven POM distributed and deployed at http://repository.jboss.org/maven2
- the logging facade is now SLF4J (aligned with Hibernate Core)
- the build system no longer rely on relative directory structures
(especially we no longer need the hibernate-3.2 directory): all
dependencies are downloaded from http://repository.jboss.org/maven2
Hibernate Search 3.1.x will also target Hibernate Core 3.3
There will probably be a CR2 fixing a couple of bugs, cleaning up
backward compatible code and updating the documentation.
Downloads available http://www.hibernate.org/30.html
Please report any defect in JIRA http://opensource.atlassian.com/projects/hibernate/secure/Dashboard.jspa
Community support in our forums http://forum.hibernate.org/
16 years, 7 months
- 1
- 0
Hibernate Core 3.3.0.CR1
by Steve Ebersole
The Hibernate team is pleased to announce the release of Hibernate
Core 3.3.0.CR1. This release features:
* a redesign of the "second level cache" SPI
* a new integration with JBossCache 2.x taking full advantage of this
new SPI (special thanks to Brian Stansberry for his help and hard work
on this)
* introduction of the org.hibernate.jdbc.Work API for performing JDBC
work without interfering with connection release modes
Another change in this release from previous releases is the switch
Maven, which has a few implications for users. The biggest is the
splitting of the project into what Maven terms modules. Essentially
we utilized modules for isolating optional features sets. For
example, there is a module for the integration of JBoss Cache 2.x as
the "second level cache". In terms of users, that means that there is
a separate jar defining that integration. But also, for those using
Maven or another library which understands its notion of transitive
dependencies, the specific dependencies of JBoss Cache 2.x are
isolated to just that module.
The Maven artifacts are deployed to the JBoss Maven repository (http://repository.jboss.org/maven2
) under the groupId of org.hibernate. The main artifactId is
hibernate-core. Over the next few days we will be writing up some
descriptions for the web site describing the various modules/
artifactIds and the purpose of each.
For those not using Maven, we do still build a dist for upload to
SourceForge: http://sourceforge.net/project/showfiles.php?group_id=40712&package_id=12...
There have been a few issues identified with the SourceForge bundles.
They have all been pretty minor and none code related. The issue with
the biggest impact is probably the fact that a few dependencies are
missing from the bundles. We have identified jta.jar, javaassist and
cglib (and its asm deps). These will be corrected for another CR and
eventual GA.
-----------------------------
Steve Ebersole
Project Lead
http://hibernate.org
steve(a)hibernate.org
16 years, 8 months
- 1
- 0
- ← Newer
- 1
- Older →