Support for prefixing resources#351
Open
Semper-Viventem wants to merge 12 commits intokezong:masterfrom
Open
Conversation
Author
|
@JeroenMols It might be interesting for you |
Owner
|
Thank you for your PR. It's a great job. |
|
It would be very helpful! I also need this) |
Author
|
Hello @kezong. Sorry for the follow-up. Did you manage to review the pull request? |
Owner
|
@Semper-Viventem Sorry, there are too many changes. In my project, which have 80+ modules, the change did not take effect, and a compilation error occurred. This function seems to be relatively independent. I think it can be an independent plugin. |
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.
In my working project, there was a problem building
fat-aar: the library depends on 30 modules, which have about 60,000 resources, and all of them were bundled into the library. Since the main project also depends on these resources, it makes no sense to rename them, and they cause conflicts in the SDK client. The standard build plugin does not support prefixing resources. This PR adds such an opportunity.Usage:
fataar { resourcePrefix = "lib_name_" }