-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
Gradle plugin 1.7.0 fails with latest Spring Boot 3.1.2, Gradle Kotlin 8.3 with "Task with name 'bootRun' not found in root project" #121
Comments
@matthewadams I had the same issue with bootRun not found after upgrading. In our case our plugins section looked like this:
The issue went away when reordering this to
So maybe try with kotlin before springboot? It seems that the openapi plugin now depends on a particular initialization order whereas previously (before 1.7.0) it did not matter. If this behavior change is intentional, it should probably be documented somewhere. |
I'm having same issue with version 1.7.0.
Looks like there is a workaround. But it's not working for combination of Spring Boot 2.7.14 & Gradle 8.1.1. |
Sure enough, reording like this got rid of the problem:
This either needs to be identified as a bug and fixed, or at least documented. Thanks! 🙏🏼 |
Any update here? |
### What's done: - fixing the task using a workaround springdoc/springdoc-openapi-gradle-plugin#121
### What's done: - fixing the task using a workaround springdoc/springdoc-openapi-gradle-plugin#121
I guess the fix (at a) Either stop using Lines 31 to 32 in e855f9c
b) Wait for both org.springframework.boot and java plugins, and massage bootRun only in case both plugins are added (see https://docs.spring.io/spring-boot/docs/current/gradle-plugin/reference/htmlsingle/#reacting-to-other-plugins.java ). For instance: plugins.withId("org.springframework.boot") { plugins.withId("java") { massageBootRunTask() } }
|
Steps to reproduce:
gradle/wrapper/gradle-wrapper.properties
:./gradlew generateOpenApiDocs
, observe failureThe text was updated successfully, but these errors were encountered: