This message was deleted.

You cannot "call" a task, you can just define dependencies between tasks. And while you can configure one task from the execution phase of another one, you shouldn't, especially in the light of upcoming configuration cache that disallows that.

Okay, so knowing that, what is a trivial solution for this?

There most probably is none. Especially as you said

-PsomeOption

which means you are not configuring a task, but you set a Gradle property. You cannot set a Gradle programmatically. You can set an

extra

property of the same name and depending on how the consumer of the property reads it, it might take precedence. But if for example the consumer uses

providers.gradleProperty

it would not be taken into account.