/**
 * Status of a feature in a build that affects Gradle behavior,
 * and may impose additional requirements on plugins or build scripts.
 * <p>
 * It is possible to check if the feature is {@link #getActive() active} in the current build.
 * The {@link #getRequested() requested} property shows whether the user opted in or opted out from the feature.
 *
 * @see BuildFeatures
 * @since 8.5
 */
@Incubating

        } else {
            gradle.allprojects(action);
        }
    }

    private boolean isIsolatedProjects() {
        return features.getIsolatedProjects().getActive().getOrElse(false);
    }

        MyReport myReport = new MyReport();
        myReport.setConfigurationCacheUsage(configCacheUsage);

        boolean isolatedProjectsActive = buildFeatures.getIsolatedProjects().getActive() // <3>
            .get(); // the active state is always defined
        if (!isolatedProjectsActive) {
            myOptionalPluginLogicIncompatibleWithIsolatedProjects();
        }
    }

        this.active = active;
    }

    @Override
    public Provider<Boolean> getRequested() {
        return requested;
    }

    @Override
    public Provider<Boolean> getActive() {
        return active;
    }

- `false` -- the user opted out from using the feature
- `undefined` -- the user neither opted in nor opted out from using the feature

The link:{javadocPath}/org/gradle/api/configuration/BuildFeature.html#getActive--[`BuildFeature.getActive()`] status of a build feature is always defined.
It represents the effective state of the feature in the build.

When the `active` provider value is:

.dropbar&&ke(this.dropbar),delete this._dropbar},events:[{name:"mouseover",delegate:function(){return this.dropdown},handler:function(t){var e=t.current,i=this.getActive();i&&i.toggle&&!Yt(i.toggle.$el,e)&&!i.tracker.movesTo(i.$el)&&i.hide(!1)}},{name:"mouseleave",el:function(){return this.dropbar},handler:function(){var t=this.getActive();t&&!this.dropdowns.some(function(t){return Mt(t,":hover")})&&t.hide()}},{name:"beforeshow",capture:!0,filter:function(){return this.dropbar},handler:function(...

Build logic or plugin implementations can detect if the configuration cache is enabled for a given build, and react to it accordingly.
The link:{javadocPath}/org/gradle/api/configuration/BuildFeature.html#getActive--[active] status of the configuration cache is provided in the corresponding link:{javadocPath}/org/gradle/api/configuration/BuildFeatures.html#getConfigurationCache--[build feature].

        @Option(option = "integerValue", description = "integer value")
        public void setIntegerValue(Integer value) {
        }

        @Option(option = "aFlag", description = "simple flag")
        public void setActive() {
        }

        @Option(option = "multiString", description = "a list of strings")
        public void setStringListValue(List<String> values) {
        }

          <version>1.0.0/1.3.0</version>
          <code>
    public boolean isActive() {
        return (getActiveString() != null) ? Boolean.parseBoolean(getActiveString()) : true;
    }

    public void setActive(boolean active) {
        setActiveString(String.valueOf(active));
    }

    public int getPort() {
        return (getPortString() != null) ? Integer.parseInt(getPortString()) : 8080;
    }

	"desert":                               "\U0001f3dc\ufe0f",
	"desert_island":                        "\U0001f3dd\ufe0f",
	"desktop_computer":                     "\U0001f5a5\ufe0f",
	"detective":                            "\U0001f575\ufe0f",
	"diamond_shape_with_a_dot_inside":      "\U0001f4a0",
	"diamonds":                             "\u2666\ufe0f",
	"diego_garcia":                         "\U0001f1e9\U0001f1ec",