Wrapper crashes and does not start if app contains application.groovy with an import statement
- Dominant language
- Groovy
- Stars
- 2.9k
- Forks
- 975
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 92
Description
To replicated behavior, add the following to any app:
`/conf/application.groovy `
```groovy
import org.springframework.security.oauth2.client.web.OAuth2AuthorizationRequestRedirectFilter
```
`build.gradle`
```groovy
dependencies {
// ...
implementation 'org.springframework.security:spring-security-oauth2-client:5.8.14'
}
```
```
./grailsw
| Error Error occurred running Grails CLI: startup failed:
Script_6aeee2e21b7e85cf1a3c4edd08792e23.groovy: 1: unable to resolve class org.springframework.security.oauth2.client.web.OAuth2AuthorizationRequestRedirectFilter
@ line 1, column 1.
import org.springframework.security.oauth2.client.web.OAuth2AuthorizationRequestRedirectFilter
^
1 error
```
Contributor guide
Research direction
Reproduce the failure by adding the application.groovy import and the Spring Security OAuth2 client dependency from the issue, then run ./grailsw. Read application.groovy, build.gradle, and the Grails wrapper startup path; done means the wrapper starts successfully with that import present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, spring
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100