Make component report task configurable without afterEvaluate

[childnode]

changing some settings by dependentComponents {} in the build.gradle works as long they are not set in an external reports.gradle file that is sourced / applied

long story short: https://gitlab.com/childno.de/bugreports/gradle-multiproject-incubating-reports

Expected Behavior

no need of a gradle.projectsEvaluated {} needed in the reports.gradle

Current Behavior

need of a gradle.projectsEvaluated {} in the reports.gradle to wrap configuration of dependentComponents (and other incubating help task, too)

somehow the internal "Help" Plugin seem to be somewhere applied later on in the configuration phase

Context

• gradle multiproject with allprojects definition
• using an external build script for organization purposes as documented in https://docs.gradle.org/current/userguide/organizing_build_logic.html#sec:configuring_using_external_script

Steps to Reproduce (for bugs)

again: have a look at the example project

[oehme]

This is due to these tasks being added by the rule engine and not Gradle's traditional configuration model. We are slowly deprecating the rule engine and will fix this problem as we go.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[stale]

This issue has been automatically closed due to inactivity. If you can reproduce this on a recent version of Gradle or if you have a good use case for this feature, please feel free to reopen the issue with steps to reproduce, a quick explanation of your use case or a high-quality pull request.