-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Fix for Maven Package Naming Convention Handling #33678
Merged
Merged
Conversation
This file contains 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
wxiaoguang
reviewed
Feb 21, 2025
f6a8384
to
189c0ed
Compare
189c0ed
to
2f5d355
Compare
And added some tests in 795b3f5, it should be right now. Without the fix, the tests fail. |
wxiaoguang
approved these changes
Feb 21, 2025
lunny
approved these changes
Feb 21, 2025
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this pull request
Feb 21, 2025
Make legacy package names could be listed and add tests --------- Co-authored-by: [email protected] <[email protected]> Co-authored-by: wxiaoguang <[email protected]>
wxiaoguang
added a commit
that referenced
this pull request
Feb 21, 2025
Backport #33678 by dianaStr7 Co-authored-by: Diana <[email protected]> Co-authored-by: [email protected] <[email protected]> Co-authored-by: wxiaoguang <[email protected]>
zjjhot
added a commit
to zjjhot/gitea
that referenced
this pull request
Feb 24, 2025
* giteaofficial/main: Fix git empty check and HEAD request (go-gitea#33690) Fix some user name usages (go-gitea#33689) Try to fix ACME path when renew (go-gitea#33668) [skip ci] Updated translations via Crowdin Improve Open-with URL encoding (go-gitea#33666) Fix for Maven Package Naming Convention Handling (go-gitea#33678) Improve swagger generation (go-gitea#33664) Deleting repository should unlink all related packages (go-gitea#33653)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport/done
All backports for this PR have been created
backport/v1.23
This PR should be backported to Gitea 1.23
lgtm/done
This PR has enough approvals to get merged. There are no important open reservations anymore.
modifies/api
This PR adds API routes or modifies them
modifies/go
Pull requests that update Go code
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
type/bug
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.
Description
This pull request addresses the bug reported in #33672 related to the handling of Maven packages with older naming conventions. The
getVersionByPackageName
method in thepackage_version
has been updated to throw an exception ErrNotExist when no packages are found. This error already was expected for the call back mechanism for maven packages for legacy name handling.Changes Made
Make legacy package names could be listed and add tests
Related Ticket