Not sure; we'd have to look to see which hash that build pulled from git. But, I can tell you it will be in today's 4.1.8 release which Brett will start in a few hours.

Btw, there were 2 issues here really rather than just one. I only addressed the invalid SQL generation. The other issue has to do with using property paths versus property names. It is not a bug and would need separate "Improvement" issue. As an example from the test I used:

Criteria criteria = s.createCriteria( Order.class );
criteria.add( Restrictions.eq( "customer.name", "Acme" ) );

tries to use a "property path" as a restriction. This instead needs to be:

Criteria criteria = s.createCriteria( Order.class );
criteria.createCriteria( "customer" ).add( Restrictions.eq( "name", "Acme" ) );