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
Document the need to use the launcher to be able to use application.* properties in a custom banner #22519
Comments
Thanks for the sample. The problem is as @philwebb described here. The change made in #21705 has not helped in your case as you are not using Spring Boot's launcher. This means that it doesn't get a chance to make it possible to load a manifest (which is the source of the application version) from a folder. You can avoid the problem by unpacking the jar and then using
I don't think there's anything we can do to improve this behaviour. When launched with a classpath of Let's update the banner customization documentation to note the restriction and recommend the use of the launcher with an exploded archive. |
application.*
properties in a custom banner
application.*
properties in a custom banner
Another option is to set the
|
@wilkinsona, thank you for the answer and suggestion! |
@wilkinsona I know this is an oldie, but mind if I update the docs for this one? |
Closing in favor of PR #24982. Thanks @robert-smith-911! |
Sorry for missing your question about updating the docs, @robert-smith-911. Thanks for opening a PR despite my lack of response. |
@wilkinsona You're welcome! |
Some of the banner properties not populated when running with unpacked jar and custom banner
When running Spring Boot application with custom banner and unpacked jar as documented in [1],
the following banner properties that described in [2] are not printed
[1] Deploying to Containers
[2] Customizing the Banner
Spring Boot version: 2.3.1.RELEASE
i saw this #21705 that looks similar issue, but i tried with 2.3.1.RELEASE version and it still does not show the values.
Example project that re-create the issue
The text was updated successfully, but these errors were encountered: