Gradle plugin: use full URI for configuration source locations #36803
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.
io.quarkus.gradle.tasks.EffectiveConfig.CombinedConfigSourceProvider
passes only the "file extension" (e.g.application.properties
) down toio.smallrye.config.AbstractLocationConfigSourceLoader#loadConfigSources(java.lang.String[], int, java.lang.ClassLoader)
, which may let that function behave wrong and try to for example access anapplication.properties
in the wrong location. This can be reproduced by placing anapplication.properties
file in the project directory of a Gradle project that uses the Quarkus Gradle plugin.This change fixes this behavior by passing down the correct locations as the
String
representation of the resource URIs, instead of just the "file extensions".Fixes #36767