[Gradle] Correctly identify all modules' group and version #1365
Conversation
This file contains 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
malice00
changed the title
Signed-off-by: Roland Asmann <roland.asmann@gmail.com>
|
@prabhu Sure, no problem! |
prabhu
approved these changes
Sep 9, 2024
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.
We build apps using Expo, which adds several modules to our build. Currently, these modules are added several times as components with different groups and versions. This PR addresses this by loading the correct data for all modules and caching it to use whenever a module is referenced instead of relying on incorrect defaults.
This PR is based on #1337, which must therefore be resolved before this can be merged.