This message was deleted.

That is the unfortunate side effect of the software model implementation. The newer core native plugin has an opposite issue where it doesn’t create any tasks that it think are not buildable which cause issue for cross-compilation. Nokee took a hybrid approach where we let the user choose the variants and create only those tasks. In theory, you could remove the tasks using

tasks.remove

but that is extremely dangerous in the sense that it’s quite easy to produce very strange error that wouldn’t tell much to the user. However, the remove feature doesn’t exists on

ModelMap

. You would probably need to use

@Validate

rule on the

TaskContainer

. It would most likely work because the

TaskContainer

is unmanaged meaning you can mutate the object in a validation rule. The rule runs after every other rules. Note that a lot of what I just said break the contract of the Software Model. I would use extreme caution with that approach.

I figured that was the answer, I'll just deal with it rather then more hacks