Use correct artifactIds in GMM, too #405
Merged
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
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.
There was already a task to rewrite the POM files associated with each instrumentation library (e.g. replacing
corewithandroid-test-corein the XML), but I overlooked that Gradle has started generating another metadata file that needed replacing: the Gradle Module Metadata. This is what is actually being preferred when Gradle resolves variants into dependencies, causing issues like #402 and #403 due to the references being wrong in there, too. This PR fixes that. Unfortunately, the GMM API is internal and most of it inaccessible, so create a "modifier" class to update the references accordingly.