-
Notifications
You must be signed in to change notification settings - Fork 26
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
Spring Boot Gradle plugin >= v2.5.0 outputs both executable fat jar and plain jar, and GAE Gradle plugin uses plain one. #1003
Comments
@polyomino-24 Just to clarity, does the GAE gradle plugin deploy the correct JAR with |
@elefeint
and when I updated Spring Boot Gradle plugin, I became unable to deploy with |
Did this work with the earlier versions of Spring Boot plugin? |
Yes, version 2.4.4 did work. |
You can set appengine.stage.artifact = 'build/libs/demo-0.0.1-SNAPSHOT.jar' I'm afraid this feature request is a very low priority for us. We accept contributions though. |
Thanks for your comment! |
Thanks for the feedback. I will leave this open. |
more friendly one: appengine {
stage {
artifact = bootJar.archiveFile.get()
}
} |
At minimum we should document these workarounds. I've run into this last year and thoroughly forgot. |
This is not a bug, but a feature request.
Spring Boot Gradle plugin in the current version generates both executable fat jar and plain jar in the default settings like
build/libs/aaa-0.0.1.jar
build/libs/aaa-0.0.1-plain.jar
, and when I run
./gradlew appengineShowConfiguration
, it shows stage artifact is plain one.My feature request is that GAE plugin will use fat one automatically without specifying artifact or disabling generating plain one.
environment:
macOS10.15.7
openjdk version "11.0.12" 2021-07-20 LTS
gradle 6.8.3
Spring Boot Gradle plugin 2.5.4
GAE Gradle plugin 2.4.2
GAE: flexible and custom runtime
reference:
https://docs.spring.io/spring-boot/docs/2.5.1/gradle-plugin/reference/htmlsingle/#packaging-executable.and-plain-archives
The text was updated successfully, but these errors were encountered: