Skip to content
New issue

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

s2-quickstart version 6.1.0 fails because there is no grails-app/conf/spring directory #970

Open
monetschemist opened this issue Nov 13, 2023 · 1 comment

Comments

@monetschemist
Copy link

Expected Behavior

After updating build.gradle with

implementation '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:

| 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

@monetschemist
Copy link
Author

Just to update the above, the same holds true with Grails 6.1.2 and Spring Security Core 6.1.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants