a plugin is responding to some configuration object exposed to build.gradle
and hence has to wait and see what value is supplied by the developer.
I have invariably used gradle.projectsEvaluated
for this in the absence of any other way to control when such things fire (this plugin is applying various defaults/conventions so is typically responding to the configuration in total)