Hi,
Could someone take a look at this, please?
The current 4.1.10-SNAPSHOT published on the snapshots repository
isn't up to date at all even if generated this night. It's at least 2
months old code.
See
https://repository.jboss.org/nexus/content/repositories/snapshots/org/hib...
and for example:
org.hibernate.engine.spi.BatchFetchQueue - which doesn't have my latest commits
or
org.hibernate.cfg.Configuration - which doesn't have these fixes by
Brett commited in december:
https://github.com/hibernate/hibernate-orm/commit/837fa8acccb1c8aabf77c01...
I would like to validate 4.1.10-SNAPSHOT to check for any further
regression before release. While I could build them here locally, I
would prefer to validate artifacts built by the "official" build
chain.
Thanks for your help.
On Mon, Feb 4, 2013 at 3:48 PM, Guillaume Smet <guillaume.smet(a)gmail.com> wrote:
Hi,
While working on HHH-7821, I wanted to use the latest 4.1.x snapshot.
However, it seems that the snapshots published aren't correct: they
don't contain the latest fixes:
See
http://snapshots.jboss.org/maven2/org/hibernate/hibernate-core/4.1.10-SNA...
(I used this URL as it's the one referenced in the gradle build file
but I have the same problem with the Nexus repository)
I noticed it because my context doesn't start anymore due to the use
of Dialect.getDialect() in Configuration. It was removed in a
following commit in branch 4.1 (
https://github.com/hibernate/hibernate-orm/commit/837fa8acccb1c8aabf77c01...
from december 19) but the snapshot still has the old version in
org/hibernate/cfg/Configuration.java at line 1563:
Dialect.getDialect().getUniqueDelegate().generateUniqueKey(
table, tableColumn );
Could someone check that the snapshot generation and deployment process are OK?
Thanks.
--
Guillaume