You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have upgraded this plugin to Grails 4. I generated a web-plugin with grails 4 installation and looked at the diff of the build.gradle for the old and new and integrated the changes. There is not much.
I ran a bootRun and it compiled fine.
However the gradlew check on all of tests almost. I did some debugging and the PreQueryListener which intercepts the gorm calls is not getting hit in any query with a breakpoint. This occurs in 3.3.x grails obviously. I see in Gorm 7.0 it is the same class and same package as in Gorm 6.1.8. I am at a loss why this would not fire the same event and register. I changed the grails 4 version for kicks to have gormVersion=6.1.8.RELEASE but to no avail as well.
I gather there is some underlying grails change that is contributing to the existing implementation of this plugin not working.
The text was updated successfully, but these errors were encountered:
niravassar
changed the title
Grails 4 upgrade has the PreQuery Listener no longer registering
Grails 4 upgrade has the PreQueryListener no longer registering
Feb 26, 2019
I have upgraded this plugin to Grails 4. I generated a web-plugin with grails 4 installation and looked at the diff of the
build.gradle
for the old and new and integrated the changes. There is not much.I ran a
bootRun
and it compiled fine.However the
gradlew check
on all of tests almost. I did some debugging and thePreQueryListener
which intercepts the gorm calls is not getting hit in any query with a breakpoint. This occurs in 3.3.x grails obviously. I see in Gorm 7.0 it is the same class and same package as in Gorm 6.1.8. I am at a loss why this would not fire the same event and register. I changed the grails 4 version for kicks to havegormVersion=6.1.8.RELEASE
but to no avail as well.I gather there is some underlying grails change that is contributing to the existing implementation of this plugin not working.
The text was updated successfully, but these errors were encountered: