javax.persistence.jdbc.dialect, javax.persistence.jdbc.driver, javax.persistence.jdbc.url, javax.persistence.jdbc.user, javax.persistence.jdbc.password and maybe some other standard JPA properties (javax.persistence.jdbc.schema?) aren't taken into account. I try to use them to replace the hibernate-specific properties in order to ease the comparison between several EJB/JPA implementations. I used these ones:
hibernate.dialect, hibernate.connection.driver_class, hibernate.connection.url, hibernate.connection.username, hibernate.connection.password.
Some exceptions are thrown when creating the entity manager factory as you can see in the enclosed files.
As you can see here, Hibernate only looks for the dialect by using only its specific property name:
Hibernate 4.3.5, Oracle 11g R2 (188.8.131.52)
This bug report does not indicate that the reported issue affects version 5.x. Versions prior to 5.x are no longer maintained. It would be a great help to the Hibernate team and community for someone to verify that the reported issue still affects version 5.x. If so, please add the 5.x version that you verified with to the list of affected-versions and attach the (preferably SSCCE) test case you used to do the verification to the report; from there the issues will be looked at during our triage meetings.
For details, see http://in.relation.to/2015/10/27/great-jira-cleanup-2015/
As part of verifying that this issue affects 5.0, please just set the "Affects version". Leave the "verify-affects-5.0" label and leave the issue in "Awaiting Response" status; these are critical for us to be able to track these verifications and triage them. Thanks.