-
-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Folder path #74
Comments
Isn't your customer a flavor dimension on its own? If so, files in |
I do not use flavorDimension, only productFlavors like:
|
Can you explain why you are overriding the default source sets? Do you have multiple customers, where each customer has those two flavors? That would be exactly what flavor dimensions are for. I could, however, think of a solution where we extend the sourceSets DSL. Something like:
But that seems a little ambitious and I don't see the real benefit for now. |
We have a base app fully customizable. We make one flavor for each customer with its own assets folder. Your solution is perfect for these cases, as each customer has his own google play info. |
Since the solution above works and changing source sets is unconventional, the original feature request is no longer needed. |
The play folder must be in
src/${flavor}/play
but there is any way to configure another path?Perhaps something like:
The text was updated successfully, but these errors were encountered: