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
./gradlew runCommand -Pargs="s2-quickstart org.myorg.myapp User Role"
should run to completion, creating the appropriate artefacts.
Actual Behaviour
Instead, s2-quickstart fails with the following message:
| Error Command execution error: grails-app/conf/spring/resources.groovy (No such file or directory)
Workaround
I have found that if I create a fresh application directory:
grails create-app org.myorg.myapp
then add the Spring security configuration line shown above into build.gradle
then issue a
mkdir grails-app/conf/spring
that the subsequent
./gradlew runCommand -Pargs="s2-quickstart org.myorg.myapp User Role"
succeeds. However, if I try creating this directory once the gradle build has failed, further errors occur.
There is probably a "clean" step in the s2-quickstart script somewhere that could be used to sort out the mess in order not to have to create a new app directory.
Steps To Reproduce
Update build.gradle as above and run s2-quickstart as above.
Environment Information
Ubuntu 23.10, latest SDKMAN installed
sdk use java 11.0.21-tem
sdk use groovy 3.0.11
sdk use grails 6.1.0
Example Application
No response
Version
6.1.0
The text was updated successfully, but these errors were encountered:
Expected Behavior
After updating
build.gradle
withimplementation 'org.grails.plugins:spring-security-core:6.1.0'
running
./gradlew runCommand -Pargs="s2-quickstart org.myorg.myapp User Role"
should run to completion, creating the appropriate artefacts.
Actual Behaviour
Instead, s2-quickstart fails with the following message:
Workaround
I have found that if I create a fresh application directory:
grails create-app org.myorg.myapp
then add the Spring security configuration line shown above into
build.gradle
then issue a
mkdir grails-app/conf/spring
that the subsequent
./gradlew runCommand -Pargs="s2-quickstart org.myorg.myapp User Role"
succeeds. However, if I try creating this directory once the gradle build has failed, further errors occur.
There is probably a "clean" step in the s2-quickstart script somewhere that could be used to sort out the mess in order not to have to create a new app directory.
Steps To Reproduce
Update
build.gradle
as above and runs2-quickstart
as above.Environment Information
Ubuntu 23.10, latest SDKMAN installed
Example Application
No response
Version
6.1.0
The text was updated successfully, but these errors were encountered: