You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 13, 2022. It is now read-only.
I have a spring boot project with Actuator installed and I wanted to setup the info endpoint to have some properties from a gradle file. So I configured gradle to processResources by adding this to my build.gradle.
processResources {
expand(project.properties)
}
Then I changed my bootstrap.yml to use placeholders for the appropriate gradle.properties like so.
info:
build:
name: ${name}
Now I'm unable to run the application via the Boot Dashboard. It looks to me like the processResources isn't being run against whatever Boot Dashboard selects to generate the artifact to run. The exception I get when the application is run would indicate that Spring is trying to handle the replacement instead of Gradle already having done the replacement.
Could not resolve placeholder 'name' in string value "${name}"
I'm not sure if this is the right place to report this issue, maybe it's a bug in the Gradle STS and Buildship plugins? I've tried both and neither of them make a difference.
The text was updated successfully, but these errors were encountered:
I've tried running via the Spring Boot Dashboard, and as a Java application. I did some additional research and it sounds to me like this is a problem with the Gradle plugins not the STS dashboard itself.
I have a spring boot project with Actuator installed and I wanted to setup the info endpoint to have some properties from a gradle file. So I configured gradle to processResources by adding this to my build.gradle.
Then I changed my bootstrap.yml to use placeholders for the appropriate gradle.properties like so.
Now I'm unable to run the application via the Boot Dashboard. It looks to me like the processResources isn't being run against whatever Boot Dashboard selects to generate the artifact to run. The exception I get when the application is run would indicate that Spring is trying to handle the replacement instead of Gradle already having done the replacement.
I'm not sure if this is the right place to report this issue, maybe it's a bug in the Gradle STS and Buildship plugins? I've tried both and neither of them make a difference.
The text was updated successfully, but these errors were encountered: