jvm-packaging

Publish signed JVM artifacts to Maven Central via Gradle.

1|1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Jylhis/skills --skill jvm-packaging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jvm-packaging
Source: https://github.com/Jylhis/skills/tree/main/skills/jvm-packaging
Command: npx skills add https://github.com/Jylhis/skills --skill jvm-packaging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Packaging and publishing JVM artifacts to Maven Central can be error-prone and time-consuming, requiring consistent configuration of Gradle plugins, artifact artifacts (sources, Javadoc), signing, and central portal integration.

Core Features & Use Cases

  • Gradle Java-library and maven-publish integration to publish artifacts to Maven Central.
  • Signing with GPG to satisfy Maven Central requirements.
  • nmcp or JReleaser support for central portal publishing and multi-target releases.
  • JPMS module support with proper module-info and artifact packaging, plus sources and Javadoc jars.
  • Use Case: release a new library to Maven Central or update metadata for an existing artifact, ensuring all artifacts are signed and documented.

Quick Start

Configure your Gradle project with the java-library, maven-publish, signing, and nmcp or JReleaser plugins, then run the release pipeline to publish to Maven Central.

Frequently Asked Questions about jvm-packaging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish a JVM library to Maven Central using Gradle?

Publishing a JVM library to Maven Central requires configuring Gradle with java-library, maven-publish, and signing plugins to produce valid POMs and artifacts. Using nmcp or JReleaser automates central portal uploads and multi-target releases.

What is needed to sign Gradle artifacts for Maven Central publication?

Signing Gradle artifacts for Maven Central requires GPG configured through the signing plugin to satisfy Central Portal validation. This cryptographically verifies your library's sources, Javadoc jars, and POM metadata.

Does this Skill support JPMS modularization when packaging JVM artifacts?

JPMS modularization is supported for packaging JVM artifacts, ensuring proper module-info integration alongside sources and Javadoc jars. This maintains valid Maven Central releases during ongoing library maintenance.

Can I use JReleaser instead of nmcp for multi-target releases to Maven Central?

You can use JReleaser instead of nmcp for multi-target releases to Maven Central. Both tools provide central portal publishing capabilities, allowing you to choose your preferred workflow for distributing JVM artifacts.

What Gradle plugins are required to streamline JVM packaging and publication?

Streamlining JVM packaging requires Gradle java-library, maven-publish, and signing plugins to generate core artifacts. Optional nmcp or JReleaser configurations produce sources, Javadoc jars, and valid POMs for Central.

Why does my Maven Central release fail due to missing sources or Javadoc jars?

Maven Central releases fail without sources or Javadoc jars because Central Portal validation requires complete documentation. Configuring Gradle packaging with nmcp or JReleaser ensures these artifacts are generated and signed correctly.