Do not include default values when passing Gradle build configuration to Quarkus #49503
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This comment has been minimized.
This comment has been minimized.
Status for workflow
|
gsmet
approved these changes
Aug 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Gradle plugin uses a separate worker process to execute Quarkus tasks. It copies all
quarkus.*configuration from the main process and hands it over to the worker as system properties. This means that everyquarkus.*configuration is set as a system property.To warn about deprecated configuration names, we check if the value is coming from the defaults. However, due to the Gradle plugin's behavior, every deprecated name will be reported because the value is set as a system property in the worker process.
This PRs removes all
quarkus.*values coming from the default source, since they are not required, and the values will be available in the Quarkus tasks.