We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
application should run with ./gradlew bootRun
./gradlew bootRun fails with: UserPasswordEncoderListener.groovy: 8: unable to resolve class grails.events.annotation.gorm.Listener
sdk use grails 6.1.1 sdk use groovy 3.0.11 sdk use java 11.0.21-sem
grails create-app test cd test create file grails-app/conf/spring/resources.groovy with content: beans = { }
./gradlew runCommand "-Pargs=s2-quickstart me.test.main User Role"
will complete
but:
./gradlew bootRun
fails
linux 22.04 sdk use grails 6.1.1 sdk use groovy 3.0.11 sdk use java 11.0.21-sem
No response
6.1.1
The text was updated successfully, but these errors were encountered:
Should be fixed when 6.1.2 is released.
Can be worked around by adding:
implementation 'org.grails.plugins:events:5.0.2' implementation 'org.grails.plugins:async:5.0.2'
Related grails/grails-core#13324 and grails/grails-core#13331
Sorry, something went wrong.
No branches or pull requests
Expected Behavior
application should run with
./gradlew bootRun
Actual Behaviour
./gradlew bootRun fails with:
UserPasswordEncoderListener.groovy: 8: unable to resolve class grails.events.annotation.gorm.Listener
Steps To Reproduce
sdk use grails 6.1.1
sdk use groovy 3.0.11
sdk use java 11.0.21-sem
grails create-app test
cd test
create file grails-app/conf/spring/resources.groovy
with content:
beans = {
}
./gradlew runCommand "-Pargs=s2-quickstart me.test.main User Role"
will complete
but:
./gradlew bootRun
fails
Environment Information
linux 22.04
sdk use grails 6.1.1
sdk use groovy 3.0.11
sdk use java 11.0.21-sem
Example Application
No response
Version
6.1.1
The text was updated successfully, but these errors were encountered: