library-publisher

Configure Gradle publishing blocks and POM metadata for Android libraries.

8|1|Updated Jun 12, 2018
One-click install
npx skills add https://github.com/SheTieJun/BaseKit --skill library-publisher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: library-publisher
Source: https://github.com/SheTieJun/BaseKit/tree/main/.trae/skills/library-publisher
Command: npx skills add https://github.com/SheTieJun/BaseKit --skill library-publisher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides Android library developers to publish their libraries using the Maven Publish plugin.

Core Features & Use Cases

  • Automated publishing configuration: configure Gradle publishing blocks and relevant metadata for AARs.
  • Metadata and repository management: define groupId, artifactId, version, licenses, developers, and publish targets for Maven Local or remote repositories.
  • Reusable distribution strategies: support single-variant publishing and multi-module fused libraries for consumers.

Quick Start

In your library module, add the maven-publish plugin and apply Android library settings, then configure the publishing block and run Gradle tasks to publish to your chosen repository.

Frequently Asked Questions about library-publisher

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

FAQPage Schema
How do I publish an Android library AAR with Maven Publish?

To publish an Android library AAR with Maven Publish, apply the com.android.library and maven-publish plugins, configure the publishing block in Gradle, define your POM metadata, and run the publish task to push the artifact to your target repository.

What Gradle POM metadata is required for publishing an Android library?

Required POM metadata for publishing an Android library includes groupId, artifactId, version, licenses, and developer information. Defining these Pom details properly ensures your published AAR artifacts are reproducible and sharable for consumers.

Can I use Maven Publish to publish multi-module Android libraries to a remote repository?

Yes, you can use Maven Publish to distribute multi-module fused Android libraries to remote repositories. The skill supports configuring single-variant publishing setups and defining remote repository targets for consumer distribution.

What's the best way to configure a release variant for Android library publishing?

The best way to configure a release variant for Android library publishing is to enforce a release variant setup within your Gradle publishing block, ensuring proper single-variant AAR generation before executing the publish task.

Why does my Android library publish task fail without the com.android.library plugin?

Your Android library publish task fails because the Maven Publish plugin requires the com.android.library plugin to properly generate AAR artifacts. Both plugins must be applied to ensure reproducible, sharable library outputs.