I didn't try to get rid of Configuration, since it's still the only way to get to
SF (new metamodel is not in place yet)
but there are others:
1. package change
3. Junit 4
Strong Liu <stliu(a)hibernate.org>
Hi, Strong Liu,
can I somehow look at you "draft" hibernate tools for hibernate core 4
You said there are a lot of code should be rewritten, I guess you try to get rid of
My approach was: minimal changes and still use the Configuration class.
06/10/2011 20:05, Strong Liu wrote:
> I'm in the middle of moving hibernate tools to use hibernate4
> but there are too many codes need to be changed (well, almost all)
> I guess you won't like my pull request :(
> Strong Liu<stliu(a)hibernate.org>
> On Oct 6, 2011, at 11:37 PM, Max Rydahl Andersen wrote:
>> On Sep 30, 2011, at 20:01, Gail Badner wrote:
>>> There have been a couple of comments about problems with eclipse integration
with Hibernate 3.6.7:
>>> - http://in.relation.to/Bloggers/HibernateCore367FinalRelease#comment21925
>>> - http://in.relation.to/Bloggers/HibernateCore367FinalRelease#comment22031
>>> I don't use Eclipse myself. Does anyone have an answer?
>> It's not just Eclipse, its any Hibernate tools usage that have the problem.
>> Hibernate 3.6 breaks API so we can't build console configurations and session
>> without recompiling and if we do that we won't work with Hibernate 3.2-3.5.
>> Same problem with Hibernate 4.
>> Now when Hibernate 4 is keeping Configuration it becomes somewhat more possible
>> Hibernate 3.5 and Hibernate 4…but its rather messy unfortunately ;(
>> Dima is working on solving some of this but its still very experimental.
>> If anyone got time to help out we very much welcome it!
>> hibernate-dev mailing list
> hibernate-dev mailing list