Re: [hibernate-dev] Backward compatibilty latest snapshot

2009-03-26 Thread Steve Ebersole
DialectFactory constituted a circular package dependency between o.h.dialect and o.h.dialect.resolver. It was moved to the o.h.dialect.resolver package to alleviate that circularity (yes we have tons of such circularity in Hibernate, but we have to start cleaning up somewhere). Sadly, even that

Re: [hibernate-dev] Backward compatibilty latest snapshot

2009-03-26 Thread Emmanuel Bernard
DialectFactory is not a public API AFAIK but I know Grails had to use a bunch of non public API esp on the mapping side. So two solutions here: - it makes sense to move back DialectFactory to the dialect package, Steve's call (note that the interface might have changed anyway - get the grai