-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Quarkus fails to resolve quarkus.application.version
in dev mode
#46718
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
Comments
quarkus.application.version
in dev mode
cc @radcortez |
Hi @slinstaedt-hlag I tried to reproduce this issue here but was not possible, could you send a minimal reproducer? |
Good day. I tried with an helloworld quarkus application and that also just works fine as you mentioned. I am currently debugging both our application and the mentioned helloworld app to figure out, what could cause the different startup behaviour. For now I can just tell, that the helloworld intializes the build config during IsolatedDevModeMain#firstStart, where the LauchMode is actually also set to DEVELOPMENT before. When debugging our application, the build config is getting initialized, when the CodeGenWatcher is getting created (9 lines before), so the LauchMode is still defaulting to NORMAL, causing the prod profile being active. I am currently investigating, what is causing this, because it does not seem to be expected IMHO. |
Okay, I found the cause. In brief: When an quarkus extension is being present, that does some code generation (e.g. avro), the build config get's initialized, before LauchMode is being set to DEVELOPMENT, causing the PROD profile being activated. Reproducer attached: Remember: You need to start the reproducer from the |
@mcruzdev are you looking into it? |
Hi @radcortez I would like to continue with this, but I do not have where I need to change. Do you have in mind where to start? |
From the exception, I suspect that the Code Generator Config is not setting (or propagating) Check around those areas... if you can't spot anything out of the ordinary, let me know, and I'll do it. |
Sorry for the delay, @radcortez. I'll give this a try today and tomorrow morning. If I don't notice anything unusual, I'll let you know. |
Good day! I tried updating our project to version 3.20.1 and updated all the necessary properties. But I suddenly get an error when building/running the project via
I am setting the env variable |
Describe the bug
When updating quarkus from 3.18.4 to 3.19.2 quarkus applications could not be started in dev mode via it's static main method, if the application's version is being referenced somewhere in it's configuration, e.g. via
As both are build-time configurations, this should not be an issue with referencing runtime-time config from build-time config.
Note: Starting the application via
mvn quarkus:dev
works as expected.Expected behavior
Should start in dev mode as it was for the 3.18.x branch.
Actual behavior
Applications fails to start in dev mode due to either provided or resolved
quarkus.application.version
:How to Reproduce?
No response
Output of
uname -a
orver
Linux NHH43414 5.15.167.4-microsoft-standard-WSL2 #1 SMP Tue Nov 5 00:21:55 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Output of
java -version
openjdk version "17.0.14" 2025-01-21
Quarkus version or git rev
3.19.2
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.8.7
Additional information
No response
The text was updated successfully, but these errors were encountered: