Fix Gradle plugin publishing by adding explicit dependency versions for POM generation#292
Merged
wodrobina merged 1 commit intoePages-de:masterfrom Mar 10, 2026
Merged
Conversation
meysamzamani
approved these changes
Mar 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change fixes a failure during the publishPlugins task when releasing the Gradle plugin.
The Gradle Plugin Publish plugin generates its own POM when pluginBundle.mavenCoordinates() is used. In that mode it requires explicit dependency versions. Several dependencies in the Gradle plugin module relied on versions provided indirectly via the Spring Boot BOM (io.spring.dependency-management). While this works for compilation, the plugin-publish process cannot resolve these versions when generating the plugin POM.
As a result, the release failed with errors like:
This PR adds explicit dependency versions so that the plugin publication can generate a complete POM and the release pipeline succeeds.