-
Notifications
You must be signed in to change notification settings - Fork 7
Duplicate artifacts at maven central (FYI) #25
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
Comments
@suraj-mathew Indeed, I know about this status and wanted to delete the old repo, just was unable to find the method - afaik, mvnrepository.com does not allow deleting. In case you know how to do it, pls let me know. |
@tkohegyi - That was a new piece of information to me, that mvn artifacts cant be deleted.. Hmm.. really strange... When i searched some links in internet, one of them mentions to try the luck by dropping a detailed email to SonaType support via the email - central-support@sonatype.com This is a genuine reason, so you can give a try (if not done already). |
Hi @suraj-mathew - thank you for the suggestion, I will give a try -> mail sent to SonaType support to remove the unused repo. |
No luck - quote from Sonatype response: Sonatype policy prevents the deletion or any other modification of artifacts after they are published to Central. If you already have a newer version released, you could inform your users about avoiding the incorrect ones. |
@tkohegyi - :-( I think you can ask them on how the red boxed entry can be added to this mitm's old link ? That way, even if someone access the old link - they will get notified to redirect. Look at this sample: https://mvnrepository.com/artifact/javax.annotation/javax.annotation-api |
Yes, this is a helping KB - https://maven.apache.org/guides/mini/guide-relocation.html |
@tkohegyi,
The maven central repository contains duplicate misleading artifact entries for this project, which seems to have got created during the initial phases of the project.
It will be great, if you can remove the old one from maven central to avoid confusion for future users.
NOTE:
I didn't find any other means to convey this message to you. That's why raised this ticket.
The text was updated successfully, but these errors were encountered: