This effectively couples the configuration of cache cleanup to the Gradle User Home those settings apply to and limits the possibility of different conflicting settings from different projects being applied to the same directory.

[[dir:gradle_user_home:multi_version_cache_cleanup]]
==== Multiple versions of Gradle sharing a Gradle User Home

                        .contextualLabel(
                            String.format(
                                "has conflicting %s annotations %s: %s",
                                category.getDisplayName(),
                                source,

    tf_executor.fetch %island#0 : tensor<32xf32>
  }
  func.return %graph : tensor<32xf32>
}

// -----
!tf_res = tensor<*x!tf_type.resource<tensor<32xf32>>>

// Tesets that the pass reports error on conflicting assignments from multiple
// callers.

func.func @error_on_conflict_multiple_callers(
  %arg0: !tf_res {tf.device = "/TPU:0"},
  %arg1: tensor<i1>) {
  tf_executor.graph {
    %island = tf_executor.island {

				// No need to provide a DNS entry for each variant.
				//
				// NOTE: This is not done for Kubernetes Multi-Cluster Services (MCS) hosts, in order
				// to avoid conflicting with the entries for the regular (cluster.local) service.
				nameInfo.Namespace = svc.Attributes.Namespace
				nameInfo.Shortname = svc.Attributes.Name
			}
			out.Table[hostName.String()] = nameInfo

  //
  // NOTE: Tie-breaking mechanism is not yet supported. Providing multiple
  // `QuantizationSpec` with conflicting quantizable units may result in
  // undefined behavior.
  // TODO: b/307620778 - Support tie-breaking for conflicting specs.
  repeated QuantizationSpec specs = 1;
}

// Configuration for quantization debugger.

        and:
        resolveArtifacts(project1) { expectFiles 'changed-module-changed.jar', 'project1-1.0.jar', 'project2-2.0.jar' }
    }

    def "reports failure when project dependency references a project with multiple conflicting publications"() {
        createBuildScripts("""
project(":project2") {
    publishing {
        publications {
            extraComponent(IvyPublication) {
                from components.java

    return TableCollectors.<T, R, C, V, I>toTable(
        rowFunction,
        columnFunction,
        valueFunction,
        (v1, v2) -> {
          throw new IllegalStateException("Conflicting values " + v1 + " and " + v2);
        },
        tableSupplier);
  }

  static <
          T extends @Nullable Object,
          R extends @Nullable Object,
          C extends @Nullable Object,

				if foundSum != "" && foundSum != h { // conflicting sums exist
					return "", false
				}
				foundSum = h
			}
		}
	}
	for _, h := range goSum.m[mod] {
		if !strings.HasPrefix(h, "h1:") {
			continue
		}
		if !goSum.status[modSum{mod, h}].dirty {
			if foundSum != "" && foundSum != h { // conflicting sums exist
				return "", false
			}
			foundSum = h
		}
	}

                contextualLabel == 'Type \'MyTask\' property \'file\' has conflicting type annotations declared: @InputFile, @OutputFile'
                details == 'The different annotations have different semantics and Gradle cannot determine which one to pick'
                solutions == [ 'Choose between one of the conflicting annotations' ]
                additionalData.asMap == [
                    'typeName' : 'MyTask',

To fix this, you must either:

- remove the input annotations from the property, or
- remove the ignoring annotation from the property.

[[conflicting_annotations]]
== Conflicting annotations

This error indicates that a property is annotated with conflicting annotations, that is to say annotations which have different, irreconciliable semantics.