Only publish with Maven POM, disable Gradle module metadata file #2586
Conversation
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.
Fixes #2540.
Following a Gradle version upgrade #2416, Gradle publishes a module metadata file by default. By default, Gradle projects preferentially use this module metadata file rather than the Maven POM.
This project edits the Maven POM in the publish task, but the same changes are not represented in the Gradle module file. This inconsistency causes the problem described in #2540.
Let's revert to the previous behaviour, have only one source of truth, and only publish the Maven POM. This PR disables the Gradle module metadata file.
You can verify that this PR disables Gradle module metadata generation with the task
gradle generateMetadataFileForGraphqlJavaPublication