Skip to content

feat: Configure Maven publishing with POM details and GPG signing - #1

Open
Kashif-E wants to merge 2 commits into
mainfrom
publishing
Open

feat: Configure Maven publishing with POM details and GPG signing#1
Kashif-E wants to merge 2 commits into
mainfrom
publishing

Conversation

@Kashif-E

Copy link
Copy Markdown
Contributor

No description provided.

@Kashif-E
Kashif-E requested a review from Copilot June 21, 2025 21:22

This comment was marked as outdated.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@Kashif-E
Kashif-E requested a review from Copilot June 21, 2025 21:23

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR configures Maven publishing for Krawler by setting up the POM details and enabling GPG signing.

  • Updated the build script to use the Maven publish plugin with Sonatype configuration.
  • Added detailed POM metadata including project details, license, and developer information.
  • Enabled publishing to Maven Central along with GPG signing for all publications.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
krawler/build.gradle.kts Replaces a legacy publication plugin with Maven publish configuration; adds a Maven publishing block with POM details and GPG signing configuration; removes JavaScript and WASM targets.
gradle.properties Minor update adding a newline.

Comment thread krawler/build.gradle.kts
Comment thread krawler/build.gradle.kts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants