// tag::prefer-settings[]
dependencyResolutionManagement {
    rulesMode = RulesMode.PREFER_SETTINGS
}
// end::prefer-settings[]

// tag::enforce-settings[]
dependencyResolutionManagement {
    rulesMode = RulesMode.FAIL_ON_PROJECT_RULES
}
// end::enforce-settings[]

// tag::prefer-projects[]
dependencyResolutionManagement {
    rulesMode = RulesMode.PREFER_PROJECT
}
// end::prefer-projects[]

// tag::prefer-settings[]
dependencyResolutionManagement {
    rulesMode = RulesMode.PREFER_SETTINGS
}
// end::prefer-settings[]

// tag::enforce-settings[]
dependencyResolutionManagement {
    rulesMode = RulesMode.FAIL_ON_PROJECT_RULES
}
// end::enforce-settings[]

// tag::prefer-projects[]
dependencyResolutionManagement {
    rulesMode = RulesMode.PREFER_PROJECT
}
// end::prefer-projects[]

	// JwtFilter returns the JWT HTTP filter to enforce the underlying authentication policy.
	// It may return nil, if no JWT validation is needed.
	JwtFilter(useExtendedJwt, clearRouteCache bool) *hcm.HttpFilter

	// AuthNFilter returns the (authn) HTTP filter to enforce the underlying authentication policy.
	// It may return nil, if no authentication is needed.

    </dependencies>
    <build>
        <plugins>
            <plugin>
                <artifactId>maven-enforcer-plugin</artifactId>
                <version>1.1.1</version>
                <executions>
                    <execution>
                        <goals>
                            <goal>enforce</goal>
                        </goals>
                        <inherited>true</inherited>

import (
	"internal/stringslite"
)

func secure() {
	initSecureMode()

	if !isSecureMode() {
		return
	}

	// When secure mode is enabled, we do one thing: enforce specific
	// environment variable values (currently we only force GOTRACEBACK=none)
	//
	// Other packages may also disable specific functionality when secure mode
	// is enabled (determined by using linkname to call isSecureMode).

	secureEnv()
}

 * The type token should be a non-instantiable and non extensible class.
 *
 * The producer side APIs in Gradle do not currently enforce (at compile-time or run-time) details or result types.
 * Over time, they will be evolved to enforce usage of correct types.
 *
 * Currently, the only reason to use structured details/results objects is to expose
 * information to the build scan plugin.

Preconditions can define and enforce conditions like:
- The test is running on Windows (`@Requires(UnitTestPreconditions.Windows)`)
- The test is running on JDK 8 compatible JDKs (`@Requires(UnitTestPreconditions.Jdk8OrLater)`)

    public static final IvyArtifactNameSerializer INSTANCE = new IvyArtifactNameSerializer();
    private IvyArtifactNameSerializer() {
        // Private to enforce singleton.
    }

    @Override
    public IvyArtifactName read(Decoder decoder) throws IOException {
        String artifactName = decoder.readString();
        String type = decoder.readString();

		// If the version that we're about to upgrade to is a released version, we should fully enforce this policy
		// If the version is a CI/dev/experimental version, it's okay to jump two minor version steps, but then require the -f flag
		if len(newK8sVersion.PreRelease()) == 0 {

  // inception, sizes were represented using 32bit which forced an implicit cap
  // on the size of the buffer. When this was refactored to use size_t (which
  // could be 64bit) we enforce that the buffer remains at most 32bit length to
  // avoid a change in behavior.
  const size_t max_length_;
};
}  // namespace mlir::TFL