"The feature flag is no longer relevant, please remove it from your settings file. " +
                "See https://docs.gradle.org/current/userguide/feature_lifecycle.html#feature_preview for more details.")

        then:
        succeeds()

        where:
        feature << FeaturePreviewsActivationFixture.inactiveFeatures()
    }

include::about_manual.adoc[leveloffset=+2]

'''

[[part:releases]]
== **RELEASES**

include::installation.adoc[leveloffset=+2]
include::compatibility.adoc[leveloffset=+2]
include::feature_lifecycle.adoc[leveloffset=+2]

[[part:running_builds]]
== **RUNNING GRADLE BUILDS**

== CORE CONCEPTS

include::gradle_basics.adoc[leveloffset=+2]
include::gradle_wrapper_basics.adoc[leveloffset=+2]

                .withAdvice("The feature flag is no longer relevant, please remove it from your settings file.")
                .willBeRemovedInGradle9()
                .withUserManual("feature_lifecycle", "feature_preview")
                .nagUser();
        }
    }

    @Override
    public void preventFromFurtherMutation() {
        dependencyResolutionManagement.preventFromFurtherMutation();

for multi-repo setups.

NOTE: This sample shows how to adopt an link:sample_publishing_convention_plugins.html[existing sample] for use with Test Suites.

IMPORTANT: Test Suites are an link:{userManualPath}/feature_lifecycle.html#sec:incubating_state[incubating] feature, and the details described here may change.

== Use case

As an example, let's say an organization produces two types of Java software - services and libraries.

for multi-repo setups.

NOTE: There is also a link:sample_incubating_publishing_convention_plugins.html[new sample] demonstrating how to use the link:{userManualPath}/feature_lifecycle.html#sec:incubating_state[incubating] link:{userManualPath}/jvm_test_suite_plugin.html[Test Suite Plugin] in this scenario.

== Use case

If the `--incubating` option is provided, Gradle will generate build scripts which may use the latest versions of APIs, which are marked `@Incubating` and remain <<feature_lifecycle.adoc#feature_lifecycle,subject to change>>. To disable this behavior, use `--no-incubating`.

[[sec:daemon_jvm_criteria]]
== Configuring the JVM to be used

NOTE: Daemon JVM discovery and criteria are <<feature_lifecycle.adoc#sec:incubating_state,incubating>> features and are subject to change in a future release.

By default, the Gradle daemon runs on the same JVM installation that started the build.

For instance, this plugin can be used to define a group of Integration Tests, which might run much longer than unit tests and have different environmental requirements.

NOTE: The JVM Test Suite plugin is an <<feature_lifecycle.adoc#sec:incubating_state,incubating>> API and is subject to change in a future release.

[[sec:jvm_test_suite_usage]]
== Usage

                <li><a href="../userguide/troubleshooting.html">Troubleshooting</a></li>
                <li><a href="../userguide/compatibility.html">Compatibility Notes</a></li>
                <li><a href="../userguide/feature_lifecycle.html">Gradle's Feature Lifecycle</a></li>
            </ul>

            <h3 id="running-gradle-builds">Running Gradle Builds</h3>
            <ul>

 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package org.gradle.util.internal;

import org.gradle.internal.featurelifecycle.IncubatingFeatureUsage;
import org.gradle.internal.featurelifecycle.LoggingIncubatingFeatureHandler;

import javax.annotation.concurrent.ThreadSafe;

@ThreadSafe
public class IncubationLogger {