Skip to content
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

${quarkus.application.version} not resolvable from application.yaml #27652

Closed
GregJohnStewart opened this issue Sep 1, 2022 · 3 comments · Fixed by #27576
Closed

${quarkus.application.version} not resolvable from application.yaml #27652

GregJohnStewart opened this issue Sep 1, 2022 · 3 comments · Fixed by #27576
Labels
area/config kind/bug Something isn't working triage/duplicate This issue or pull request already exists
Milestone

Comments

@GregJohnStewart
Copy link
Contributor

Describe the bug

As the title says, ${quarkus.application.version} is no longer resolvable in the application.yaml, and produces the following error:

java.util.NoSuchElementException: SRCFG00011: Could not expand value quarkus.application.version in property

All other values populated using ${} in my yaml populate just fine, just specifically quarkus.application.version has issues,

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

Make an application.yaml (Or .properties, presumably?), and use the reference ${quarkus.application.version} in a value. Try to start the service in quarkusDev.

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

2.12.0

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

@GregJohnStewart GregJohnStewart added the kind/bug Something isn't working label Sep 1, 2022
@geoand
Copy link
Contributor

geoand commented Sep 1, 2022

@radcortez I think you've seen something similar, right?

@ThoSap
Copy link

ThoSap commented Sep 1, 2022

I have the same issue in combination with Kubernetes + Container-Image since Quarkus 2.12.0.Final:

quarkus.container-image.tag=${quarkus.application.version}-native-distroless
quarkus.kubernetes.version=${quarkus.application.version}

@radcortez
Copy link
Member

This is a duplicate of #27377. Already fixed by #27576.

@radcortez radcortez linked a pull request Sep 1, 2022 that will close this issue
@geoand geoand added the triage/duplicate This issue or pull request already exists label Sep 1, 2022
@gsmet gsmet added this to the 2.12.1.Final milestone Sep 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/config kind/bug Something isn't working triage/duplicate This issue or pull request already exists
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants