Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
maven-central-publish
Provides a standardized Maven workflow to publish Java artifacts to Maven Central using GPG signing and the modern Central Portal plugin.
skill openclawclawhub Free
Provides a standardized Maven workflow to publish Java artifacts to Maven Central using GPG signing and the modern Central Portal plugin.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, templates/pom-plugins.xml, templates/settings.xml
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- MISAKIGA
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Maven Central Publish Skill
This skill provides a standardized workflow for publishing Java/Kotlin libraries to the Maven Central Repository using the modern Central Portal (via central-publishing-maven-plugin).
๐ Prerequisites
Central Portal Account: Sign up at central.sonatype.com. Namespace Verified: You must have verified your groupId (e.g., io.github.username or com.yourdomain) in the portal. User Token: Generated from the Central Portal (My Account -> Generate User Token).
1. Install Tools
Ensure maven, gnupg, and openjdk-17+ are installed. # Ubuntu/Debian apt-get install -y maven gnupg openjdk-17-jdk
2. GPG Configuration (Critical)
Maven requires GPG signing. For automated/headless environments, Loopback Pinentry is required. # 1. Generate Key (if none exists) gpg --gen-key # 2. Configure Loopback (Prevent UI prompts) mkdir -p ~/.gnupg echo "allow-loopback-pinentry" >> ~/.gnupg/gpg-agent.conf echo "pinentry-mode loopback" >> ~/.gnupg/gpg.conf gpg-connect-agent reloadagent /bye # 3. Publish Key gpg --list-keys # Get your Key ID (last 8 chars or full hex) gpg --keyserver keyserver.ubuntu.com --send-keys <KEY_ID>
3. Maven Settings (~/.m2/settings.xml)
Configure your Central Portal credentials. <settings> <servers> <server> <id>central</id> <username>USER_TOKEN_USERNAME</username> <password>USER_TOKEN_PASSWORD</password> </server> </servers> <profiles> <profile> <id>release</id> <activation> <activeByDefault>false</activeByDefault> </activation> <properties> <gpg.executable>gpg</gpg.executable> <gpg.passphrase>YOUR_GPG_PASSPHRASE</gpg.passphrase> </properties> </profile> </profiles> </settings>
๐ฆ Project Configuration (pom.xml)
Your project MUST meet the Quality Requirements: Coordinates: groupId, artifactId, version. Metadata: name, description, url, licenses, developers, scm. Plugins: Javadoc, Source, GPG, and Central Publishing.
Recommended Plugin Configuration
Add this to your <build><plugins> section: <!-- 1. Source Plugin --> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-source-plugin</artifactId> <version>3.3.0</version> <executions> <execution> <id>attach-sources</id> <goals><goal>jar-no-fork</goal></goals> </execution> </executions> </plugin> <!-- 2. Javadoc Plugin --> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-javadoc-plugin</artifactId> <version>3.6.3</version> <configuration> <doclint>none</doclint> <!-- Prevent strict checks failing build --> <failOnError>false</failOnError> </configuration> <executions> <execution> <id>attach-javadocs</id> <goals><goal>jar</goal></goals> </execution> </executions> </plugin> <!-- 3. GPG Plugin (Best Practice: wrap in 'release' profile) --> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-gpg-plugin</artifactId> <version>3.1.0</version> <configuration> <gpgArguments> <arg>--pinentry-mode</arg> <arg>loopback</arg> </gpgArguments> </configuration> <executions> <execution> <id>sign-artifacts</id> <phase>verify</phase> <goals><goal>sign</goal></goals> </execution> </executions> </plugin> <!-- 4. Central Publishing Plugin (The Magic Sauce) --> <plugin> <groupId>org.sonatype.central</groupId> <artifactId>central-publishing-maven-plugin</artifactId> <version>0.7.0</version> <extensions>true</extensions> <configuration> <publishingServerId>central</publishingServerId> <!-- autoPublish: set to true to skip manual button click in portal --> <autoPublish>false</autoPublish> </configuration> </plugin>
๐ Deployment
Run the deploy command with the release profile active: mvn clean deploy -P release Success Indicators: [INFO] Uploaded bundle successfully... [INFO] Deployment ... has been validated. If autoPublish is false (recommended for first time), log in to central.sonatype.com, review the deployment, and click Publish.
โ Troubleshooting
ErrorCauseFix401 UnauthorizedInvalid User Token in settings.xmlGenerate new token in Central Portal. Ensure server ID matches.GPG signing failedNo pinentry / wrong passphraseUse pinentry-mode loopback config; Check gpg-agent.Javadoc generation failedStrict HTML checksAdd <doclint>none</doclint> to javadoc plugin config.Invalid coordinatesGroupId mismatchEnsure pom.xml groupId matches verified namespace in Portal.
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
2 Files1 Docs
- SKILL.md
- templates/pom-plugins.xml
- templates/settings.xml