Configuration avoidance
(Gradle 4.9+) Detects usage of API that interacts with tasks eagerly.
Eager interaction with tasks implies some inconveniences:
The user should manually set up all dependencies between tasks;
In the configuration phase, all the tasks accessed via the eager API become configured, even if they are not executed afterwards. It results in performance degradation.
Eventually, the eager API will be deprecated in favor of the lazy one.
For a migration guide, see the Gradle documentation.
Example:
Locating this inspection
- By ID
Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.
ConfigurationAvoidance- Via Settings dialog
Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.
Suppressing Inspection
You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:
More detailed instructions as well as other ways and options that you have can be found in the product documentation:
Inspection Details | |
|---|---|
By default bundled with: |