A more complex example #2
Open
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.
When dealing with flavors inside libraries, sub-libraries, and using one library vs another one, things in Gradle get pretty complex fast. Struggled with it for several days until we chanced upon your example code and used it to expand it to suit our needs. Figured a pull request to show you what we came up with that worked is "thank you" for inspiring us to reach new heights. :)
Basically, there is two flavors, "dev" and "prod" which will load up MyLib using those flavors which will then either load up SubLib1 or SubLib2, depending on the flavor. Two more flavors were added to mimic an application where the app is basically a shell and a library contains most of the app code, named AppAsLib here in the example. So "applibdev" and "applibprod" will load up AppLib which loads MyLib and then SubLib1 or SubLib2 depending on the dev/prod flavor.