Automatic publishing of Maven artifacts.
Open
Nobody has claimed this yet.
java
- Dominant language
- C
- Stars
- 1k
- Forks
- 194
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 15
Description
Maven artifacts should be automatically published in the same way as the other release packages (gem, npm, crate). However there are some open questions about how to do this:
- Whose auth information should be used to push to the
org.ruby-langnamespace on Central? I have been using mine for manual builds. I believe only @hsbt and I have access currently. - What GPG key should be used to sign the artifacts and how should that be managed? Maven Central requires all artifacts to be digitally signed. Again, I have just been using my own key for releases thusfar.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how the existing gem, npm, and crate release packages are automatically published. Then investigate Maven Central's authentication and GPG signing requirements, including ownership of the org.ruby-lang credentials and signing key. Done means Maven artifacts are automatically published and signed with an agreed credential-management approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, release, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100