Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Declare central.sonatype.com as a repository origin once setup-java supports it

Open
  • Is something wrong?
#841 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, java, kotlin
Domain
build-system, ci-cd

Research direction

First check whether a released version of actions/setup-java includes mvn-server-repository-origins. Then read snapshot.yml and inspect release.yml and github-build.sh for affected release deployment configuration. Done means the publish workflow declares the Central Sonatype origin, the snapshot deploy no longer disables credential scoping, and any affected release deployment is configured too.

Written by the indexing model from the issue text.

Description

#840 works around the Maven 3.10 credential scoping change by passing -Dmaven.repository.credentialScope=id to the snapshot deploy. That turns the new scoping off instead of configuring it.

setup-java added a mvn-server-repository-origins input in actions/setup-java#1282 (merged 2026-10-07), but it isn't in a release yet (latest is v6.0.1).

Once it's released:

  • Bump actions/setup-java to the release that includes it
  • Add mvn-server-repository-origins: central:https://central.sonatype.com to the publish job in snapshot.yml
  • Remove -Dmaven.repository.credentialScope=id from the snapshot deploy
  • Check whether the release deploy (release.yml / github-build.sh) is affected and add the origin there too

References: Maven 3.10.0 release notes

Dominant language
Kotlin
Stars
824
Forks
175
Avg merge
2d 5h
Merged PRs (30d)
53

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from graphql-java-kickstart/graphql-java-tools

All issues in graphql-java-kickstart/graphql-java-tools

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.