View post: Envers moves to Hibernate!
Navigation
Recent posts from all feeds
- hSenid - officially certified JBCP partner
- jBPM 3 seam/jsf/richfaces based console
- Help push the open sourcing of a jBPM Migration Tool
- JBUG Munich meets Pete Muir with JSR-299 - Contexts and Dependency Injection for Java EE (06.07.09 at 19:00 PM)
- Javarsovia, static analysis and annotations
- Drools Job requested - Buenos Aires Argentina
- Seam and Web Beans downloads temporarily relocated
- Introducing a new smart forms tool: Drools Advisor
- JBoss Cloud introduction video
- Using rich:colorPicker in RichFaces
- « Back to feed: Blog of Adam Warski
Envers moves to Hibernate!
I’m happy to announce that Envers is now a module of Hibernate! This means that:
-
the code is now in the hibernate-core repository (
enversmodule). There will be no more commits to the old repository. - issue tracking moved to Hibernate’s JIRA. All open issues from the old JIRA have been moved there. When creating an Envers issue, please select the “envers” component.
- envers is now built using maven2, which replaces the old ant build
The website, documentation and forum so far stay unchanged, but stay tuned for more updates :).
There will be some changes to Envers coming with this move. One of them is renaming of @Versioned to @Audited, to avoid confusion with the @Version annotation used in JPA for optimistic locking. The old @Versioned annotation will become deprecated, and after some time removed completely.
I would like to thank Steve Ebersole for doing the actual move and creating the maven build!
Adam
Post to DZone
Post to del.icio.us
Digg this!
Stumble It!