Stale maven-metadata.xml #1043
Assignees
Comments
|
This is Maven Central/Sonatype related, strangely versions missing are missing published date metadata as well: |
ben-manes
added a commit
to ben-manes/caffeine
that referenced
this issue
Sep 4, 2023
The minimum version is the first Guava release with JPMS support by including Automatic-Module-Name in the manifest. Also removed workaround for ops4j/org.ops4j.pax.exam#1043
|
Confirmed! Thanks for the fix, it removes an ugly workaround. |
ben-manes
added a commit
to ben-manes/caffeine
that referenced
this issue
Sep 5, 2023
The minimum version is the first Guava release with JPMS support by including Automatic-Module-Name in the manifest. Also removed workaround for ops4j/org.ops4j.pax.exam#1043
|
I ran a dependency updates and observe this problem again. It seems to have coincided with your release. The following dependencies exceed the version found at the milestone revision level:
- org.ops4j.pax.exam:pax-exam-container-native [4.13.5 <- 4.13.1]
http://team.ops4j.org/wiki/display/paxexam/
- org.ops4j.pax.exam:pax-exam-junit4 [4.13.5 <- 4.13.1]
http://team.ops4j.org/wiki/display/paxexam/
- org.ops4j.pax.exam:pax-exam-link-mvn [4.13.5 <- 4.13.1]
http://team.ops4j.org/wiki/display/paxexam/The maven-metadata.xml says the latest is Forwarded to central-support@sonatype.com |
|
@ben-manes, as there is no public issue tracker anymore please add any response from Sonatype here. |
|
From: Support central-support@sonatype.com Hello Ben, Thanks for bringing this to our attention, the missing versions have been fixed in maven metadata. Regards, |
|
It's still broken (https://repo1.maven.org/maven2/org/ops4j/pax/exam/): |
|
Thank you. Unfortunately, the maintainers noticed it is still broken for
their other artifacts (cc'd).
…On Mon, Dec 2, 2024 at 8:27 AM Support ***@***.***> wrote:
Hello Ben,
Thanks for bringing this to our attention, the missing versions have been
fixed in maven metadata.
Regards,
The Central Team
This email is a service from Central Support by Sonatype. Delivered by
Zendesk
<https://www.zendesk.com/support/?utm_campaign=text&utm_content=Central+Support+by+Sonatype&utm_medium=poweredbyzendesk&utm_source=email-notification>
On December 1, 2024 at 6:42:19 PM UTC, ***@***.*** wrote:
There appears to be a regression of OSSRH-94539 (pax.exam#1043
<#1043>) of stale
metadata being sync'd to Central. Those issues include the previous
investigation which, iirc, were due to a stale backup/restore process.
---
I ran a dependency updates and observe this problem again. It seems to
have coincided with your release.
The following dependencies exceed the version found at the milestone
revision level:
- org.ops4j.pax.exam:pax-exam-container-native [4.13.5 <- 4.13.1]
http://team.ops4j.org/wiki/display/paxexam/
- org.ops4j.pax.exam:pax-exam-junit4 [4.13.5 <- 4.13.1]
http://team.ops4j.org/wiki/display/paxexam/
- org.ops4j.pax.exam:pax-exam-link-mvn [4.13.5 <- 4.13.1]
http://team.ops4j.org/wiki/display/paxexam/
The maven-metadata.xml
<https://repo1.maven.org/maven2/org/ops4j/pax/exam/pax-exam-container-native/maven-metadata.xml>
says the latest is *4.13.1* and has the timestamp *2018-12-09*. The
recent *4.14.0.0* has no directory timestamp like the above. It seems to
be a regression on Central.
To unsubscribe from this group and stop receiving emails from it, send an
email to ***@***.***
[7L6KPE-DWVME]
|
|
@oliverlietz they asked to review the modules with you so I cc'd using the info email address from your git commit. |
|
Root cause (old sync with outdated OPS4J staging repo) is fixed. |
|
fwiw, I think that is private to Apache members. Thanks for helping get this resolved. |
|
@ben-manes, Access to ASF Slack is managed via invitations to prevent spamming. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On Maven Central, the published maven-metadata.xml lists up to version
4.13.1and declares it as the latest. However, the repository contains4.13.4, which the search ui lists as the latest. When using tools that scan for dependency upgrades, this causes incorrect suggestions due to the outdated metadata. Somehow your release process is no longer publishing updates.The text was updated successfully, but these errors were encountered: