Reduce unnecessary Maven repository lookups - #80
Merged
Merged
Conversation
BenCodez
force-pushed
the
build/restrict-maven-repositories
branch
from
August 23, 2026 19:23
4afa6cf to
1bc781f
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
oss.sonatype.org/content/groups/publicpseudo-central repository with real Maven Centraloss.sonatype.orgBungeeCord snapshot repositoryadvancedcoredependency from3.8.1-SNAPSHOTto3.8.2-SNAPSHOTWhy
VotingPlugin builds stalled on legacy/unrelated Maven repositories, including
oss.sonatype.org. GraveStonesPlus had the same two Sonatype repository definitions directly in its POM, so it was exposed to the same failure mode.The first CI run for this PR also exposed a separate cold-cache problem:
3.8.1-SNAPSHOTmetadata on the BenCodez Nexus pointed at timestamped AdvancedCore build3.8.1-20260607.202919-66, but that artifact/POM is no longer present. Jenkins could mask this with an existing local Maven cache. GraveStonesPlus now targets the current3.8.2-SNAPSHOT, which is available from the BenCodez repository.The failed run also showed ~20-second misses against the Velocity repository for unrelated dependencies. GraveStonesPlus has no direct Velocity dependency, so that repository is removed instead of remaining in the resolution chain.