Skip to content

Remove legacy plugin ID and fix signing for Gradle Plugin Portal - #31

Merged
AkaZver merged 1 commit into
masterfrom
feature/update-29.07.2026-4
Jul 29, 2026
Merged

Remove legacy plugin ID and fix signing for Gradle Plugin Portal#31
AkaZver merged 1 commit into
masterfrom
feature/update-29.07.2026-4

Conversation

@AkaZver

@AkaZver AkaZver commented Jul 29, 2026

Copy link
Copy Markdown
Owner

Summary

Fix both publishing failures by removing the legacy plugin ID and adding signing keys to the Gradle Plugin Portal job.

Problem

After migrating to com.vanniktech.maven.publish, both publishing jobs failed:

  1. Gradle Plugin Portal: Cannot perform signing task because it has no configured signatory

    • The vanniktech plugin's signAllPublications() tried to sign plugin marker publications, but the job had no signing keys configured
  2. Maven Central: Namespace 'com.github.akazver.mapstruct' is not allowed

    • The legacy plugin ID com.github.akazver.mapstruct created a plugin marker publication that was being published to Maven Central, but this namespace is not registered

Changes

build.gradle

  • Remove mapstructLegacy plugin definition (breaking change)
  • Only io.github.akazver.mapstruct plugin ID remains

.github/workflows/main.yml

  • Add ORG_GRADLE_PROJECT_signingInMemoryKey and ORG_GRADLE_PROJECT_signingInMemoryKeyPassword to the publish-gradle-portal job
  • This allows the vanniktech plugin to sign plugin marker publications

README.md

  • Remove migration section (no longer needed with single plugin ID)

Testing

  • ./gradlew clean build — BUILD SUCCESSFUL
  • Configuration is correct, all tests pass

Breaking Change

Users currently using com.github.akazver.mapstruct will need to update to io.github.akazver.mapstruct. This is necessary because:

  • The old namespace is not registered in Maven Central
  • Maintaining two plugin IDs adds complexity and confusion

Next Steps

After merging:

  1. Create tag 2.0.4 to test the fixes
  2. Verify both Gradle Plugin Portal and Maven Central publishing succeed
  3. Ensure artifacts appear on mvnrepository.com

- Remove mapstructLegacy plugin (com.github.akazver.mapstruct) - only io.github.akazver.mapstruct remains
- Add signing keys to publish-gradle-portal job (required by vanniktech plugin)
- Remove migration section from README (no longer needed)

This fixes both publishing failures:
- Gradle Plugin Portal: signing tasks now have configured signatory
- Maven Central: no more 'Namespace com.github.akazver.mapstruct is not allowed' error
@AkaZver AkaZver self-assigned this Jul 29, 2026
@AkaZver AkaZver added the bug Something isn't working label Jul 29, 2026
@sonarqubecloud

Copy link
Copy Markdown

@AkaZver
AkaZver merged commit 257a0b7 into master Jul 29, 2026
6 checks passed
@AkaZver
AkaZver deleted the feature/update-29.07.2026-4 branch July 29, 2026 08:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant