Quote:
I don't know if the removal was intentional and distincts are treated somewhere else now.
For me it looks very like a unintentional bug, because
Code:
toSqlString(Criteria criteria, int position, CriteriaQuery criteriaQuery)
is now implemented in CountProjections superclass AggregateProjection solely
where the distinct property is not handled at all.
I suggest you to implement an appropriate junit-test-case and to open an issue on Hibernate Jira.
Such issue should be threated with absolutely priority, as this bug compromises 3.5 backward compatibility.