The previously reported problem with Grails/JDK 1.7.0_25 compatibility
seems to be specific to OpenJDK. As soon as the one replaces OpenJDK
with Oracle JDK, error is gone and Grails applications could be started
again.
Показаны сообщения с ярлыком grails. Показать все сообщения
Показаны сообщения с ярлыком grails. Показать все сообщения
пятница, 19 июля 2013 г.
среда, 17 июля 2013 г.
Change in JDK 1.7.0_25 breaks all grails applications:
https://bugzilla.redhat.com/show_bug.cgi?id=976693
I just tried grails 2.2.3 - the problem is still not fixed, the application fails to start with an error message "Could not determine Hibernate dialect for database name [H2]".
Any workarounds suggesting to replace hibernate libraries don't work.
The following additional parameter allows to start grails:
grails -noreloading run-app
But hey, it's no fun to start in no-reloading mode! Oracle, but things back!
https://bugzilla.redhat.com/show_bug.cgi?id=976693
I just tried grails 2.2.3 - the problem is still not fixed, the application fails to start with an error message "Could not determine Hibernate dialect for database name [H2]".
Any workarounds suggesting to replace hibernate libraries don't work.
The following additional parameter allows to start grails:
grails -noreloading run-app
But hey, it's no fun to start in no-reloading mode! Oracle, but things back!
Подписаться на:
Сообщения (Atom)