Resolve gradle user home misconfiguration #28624
Merged
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.
Resolves issue: #20928
Traditionally happens against a CI pipeline with a custom gradle user home.
The issue occurs when extensions such as
quarkus-jacoco
attempt to load an ApplicationModel and the project being used:~./gradle
gradle.properties
(traditionally something likerepoUsername
andrepoPassword
) in order to resolve dependencies from a private repository.As a result of the custom gradle.properties file missed, the user is presented with errors related to missing gradle properties or not being able to resolve dependencies.