Skip to content

Resolve ItemsAdder from Maven Central and scope Oraxen and Nexo repos - #3083

Merged
tastybento merged 2 commits into
developfrom
build/scope-vendor-repos
Sep 19, 2026
Merged

tastybento merged 2 commits into
developfrom
build/scope-vendor-repos

Conversation

@tastybento

@tastybento tastybento commented Sep 19, 2026 •

Copy link
Copy Markdown
Member

Problem

CI on #3082 failed twice in compileJava dependency resolution (run):

> Could not GET 'https://maven.devs.beer/dev/lone/api-itemsadder/.../api-itemsadder-4.0.2-beta-release-11.pom'. Received status code 522
> Could not GET 'https://maven.devs.beer/world/bentobox/level/2.21.3-SNAPSHOT/maven-metadata.xml'. Received status code 522
> Could not GET 'https://maven.devs.beer/com/nexomc/nexo/1.19.1/nexo-1.19.1.pom'. Received status code 522
> Could not GET 'https://maven.devs.beer/io/th0rgal/oraxen/1.193.1/oraxen-1.193.1.pom'. Received status code 522

maven.devs.beer (the old ItemsAdder repo) is behind Cloudflare and its origin has been unreachable. Because it was declared as an unscoped repository, Gradle queried it for every artifact in order, and a 522 is a hard error rather than a miss. So resolution aborted for Level, Nexo and Oraxen before their actual repositories were reached.

Fix

ItemsAdder moves to Maven Central. ItemsAdder now publishes its API as beer.devs:itemsadder-api on Central (author's snippet page). The API package is unchanged (dev.lone.itemsadder.api), so only the coordinates change. Bumped to the latest stable release, 4.0.17, and removed the maven.devs.beer repository entirely.

Oraxen and Nexo repos are scoped. repo.oraxen.com and repo.nexomc.com move into exclusiveContent blocks limited to the groups they host (io.th0rgal, com.nexomc), matching the existing pattern for Dynmap, MomiRealms, FancyInnovations, Pyr and Clojars. Nexo's repo also hosts its team.unnamed (creative-*) transitives, so that group is included in the Nexo filter. A fragile vendor host can no longer take unrelated artifacts down with it.

Verification

  • dependencies --refresh-dependencies on compileClasspath: zero unresolved artifacts, with maven.devs.beer still returning 522.
  • compileJava compileTestJava: passes against itemsadder-api:4.0.17.
  • DefaultPasteUtilTest (the only test touching ItemsAdder): 34 tests, 0 failures.

🤖 Generated with Claude Code

tastybento and others added 2 commits September 19, 2026 19:27
maven.devs.beer, repo.oraxen.com and repo.nexomc.com were declared as
unscoped repositories, so Gradle queried them for every artifact in
order. When maven.devs.beer returned HTTP 522, resolution aborted for
Level, Nexo and Oraxen before their real repositories were reached,
failing CI on PR #3082 for artifacts that host does not serve.

Move the three repos into exclusiveContent blocks, matching the
existing pattern for Dynmap, MomiRealms, FancyInnovations, Pyr and
Clojars. Nexo's repo also hosts its team.unnamed transitives, so that
group is included in the Nexo filter.

With the host still down, a --refresh-dependencies resolution now
fails only for dev.lone:api-itemsadder.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
ItemsAdder now publishes its API to Maven Central as
beer.devs:itemsadder-api, per the author's dependency snippet page
(https://maven-snippets.lonedev.workers.dev/?pkg=beer.devs%3Aitemsadder-api).
The API package is unchanged (dev.lone.itemsadder.api), so only the
coordinates change. Move to the latest stable release, 4.0.17, and
drop the maven.devs.beer repository, which has been returning HTTP 522
and was the last thing blocking CI.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@tastybento tastybento changed the title Scope ItemsAdder, Oraxen and Nexo repos to the groups they host Resolve ItemsAdder from Maven Central and scope Oraxen and Nexo repos Sep 19, 2026
@sonarqubecloud

Copy link
Copy Markdown

@tastybento
tastybento merged commit ecc5a91 into develop Sep 19, 2026
3 checks passed
@tastybento
tastybento deleted the build/scope-vendor-repos branch September 19, 2026 18:45
@tastybento tastybento mentioned this pull request Sep 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant