when:
        EclipseProject rootProject = loadToolingModel(EclipseProject)
        def natures = rootProject.projectNatures.collect{ it.id }

        then:
        if (plugins.contains('ear') && targetVersion < GradleVersion.version("8.0") ) {
            assert natures == WTP_NATURES
        } else {
            assert natures == JAVA_NATURES + WTP_NATURES
        }

        where:
        plugins << [

    }
  }
  return same_cluster_ops_with_dependency;
}

// An op can be merged into cluster if it satisfies both of the following
// conditions:
//
//  * Merging the op into the cluster doesn't break the acyclic nature of the
//  *   graph. This means all of its operands don't have data dependency of the
//  *   cluster.
//  * Merging the op into the cluster does not reorder control dependencies.
//
bool CanMergeIntoCluster(

                    nestedPluginB,
                    nestedPluginC,
                    // plugins with ids prefixed by other plugin ids
                    // cannot be properly supported due to the side-effecting nature
                    // of `PluginDependenciesSpec#id`
                    PluginTree.PluginSpec("flat-plugin.conflict", "IgnoredPlugin"),
                    PluginTree.PluginSpec("nested.plugin-a.conflict", "IgnoredPlugin")

 * <p>
 * This class can hold a null value.
 */
@ThreadSafe
public interface CalculatedValue<T> {
    // TODO(https://github.com/gradle/gradle/issues/24767): with JSpecify, the nullable nature of the type argument <T> should be expressed as <T extends @Nullable Object>.

    /**
     * Returns the value, failing if it has not been calculated.

  // written".
  LogicalResult AnalyzeRegion(Region& region);

  // If an op is not one of the handled ones, we assume all resource usages
  // within its purview are mutating in nature.
  void PropagatePotentiallyWrittenWithinUnhandledOp(Operation* op);

  // Given a Region associated with the callee and operands from the
  // corresponding callOp, propagate the potentially written decision to the

                    artifact.getGroupId(), artifact.getArtifactId(), MAVEN_METADATA_XML, Metadata.Nature.RELEASE);
        } else if (LATEST.equals(version)) {
            metadata = new DefaultMetadata(
                    artifact.getGroupId(),
                    artifact.getArtifactId(),
                    MAVEN_METADATA_XML,
                    Metadata.Nature.RELEASE_OR_SNAPSHOT);
        } else if (version.endsWith(SNAPSHOT)) {

// will fail after the year 2262. Sorry, you'll need to upgrade to a newer version
// of Istio at that time :-)
//
// This code does some trickery with finalizers in order to avoid the need for a Close
// method. Given the nature of this code, forgetting to call Close on one of these objects
// can lead to a substantial permanent memory leak in a process by causing the cache to

                    artifact.getGroupId(), artifact.getArtifactId(), MAVEN_METADATA_XML, Metadata.Nature.RELEASE);
        } else if (LATEST.equals(version)) {
            metadata = new DefaultMetadata(
                    artifact.getGroupId(),
                    artifact.getArtifactId(),
                    MAVEN_METADATA_XML,
                    Metadata.Nature.RELEASE_OR_SNAPSHOT);
        } else if (version.endsWith(SNAPSHOT)) {

```

where "usability.observability.status" is the feature, and "exist-by-default" is the scenario in the first case, and the second case has no scenario.

We make changes to Guava's public [APIs][], including adding new APIs, very
carefully. Because of this, if you're interested in seeing a new feature in
Guava, the best approach is to create an [issue][] (or comment on an existing
issue if there is one) requesting the feature and describing specific use cases
for it.

If the feature has merit, it will go through a thorough process of API design
and review. Any code should come after this.