Fix plugin prefix resolution when metadata is not available from repository #11290
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
…sitory Restore the mechanism to load prefixes from configured plugins and use it when the prefix cannot be found from the repository. Fixes apache#11252 (cherry picked from commit 0621de2)
slawekjaranowski
force-pushed
the
plugin-prefix-resolution-3.x
branch
from
9a72c95 to
8eba513
Compare
cstamas
approved these changes
Oct 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Restore the mechanism to load prefixes from configured plugins and use it when the prefix cannot be found from the repository.
Fixes #11252
(cherry picked from commit 0621de2)