Fix project dependency artifactId resolution in pom generation logic.#12596
Merged
jaynewstrom-stripe merged 1 commit intomasterfrom Mar 10, 2026
Merged
Conversation
Contributor
|
Diffuse output: APK |
tjclawson-stripe
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
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.
Summary
Fixed the project dependency artifactId resolution in pom generation logic within deploy.gradle. Now, the artifactId is correctly used when generating the pom for project dependencies.
Motivation
Previously, project dependencies could resolve to the incorrect artifactId ("unspecified" or default project name) in generated pom files due to not handling the project artifactId property properly. This change ensures consistency in published artifacts and avoids potential downstream dependency resolution issues.
Testing
Changelog
Fixes #12595