Gradle builds too many flavors

(Jonas) #1

Let’s say I have multiple flavors, flavora, flavorb. They have different dependencies (i.e. using compileFlavora(...) and compileFlavorb(...)).

Because of these dependencies, I know that flavor A builds, but flavor B fails. I really need to build flavor A, so I run gradle assembleFlavoraDebug. The build fails, because gradle also tries to compile flavor B, which is failing.

Is it normal behavior? Isn’t it overkill (in my case even impractical) to compile all the flavors when the task explicitly asks for one and only one?