allocmLock.lock()

	// Disable preemption, preventing us from changing Ms, as we handle
	// this M specially.
	//
	// N.B. STW and lock() above do this as well, this is added for extra
	// clarity.
	acquirem()

	// N.B. allocmLock also prevents concurrent execution of this function,
	// serializing use of perThreadSyscall, mp.needPerThreadSyscall, and

	}
	if namespace == "k8s.io" || strings.HasSuffix(namespace, ".k8s.io") {
		return true
	}
	return false
}

func getLabelNamespace(key string) string {
	if parts := strings.SplitN(key, "/", 2); len(parts) == 2 {
		return parts[0]
	}
	return ""
}

// NewKubeletConfiguration will create a new KubeletConfiguration with default values

now works automatically for any source set that defines a module by containing a `module-info.java` file.
Usually, this is the behavior you need.
If this is causing issues in cases you manually configure the module path, or use a 3rd party plugin for it, you can still opt out of this by setting `modularity.inferModulePath` to `false` on the java extension or individual tasks.

==== Removal of `ValidateTaskProperties`

 * Easier integration with other parts of the build, such as dependency configurations
 * More idiomatic build scripts

It can be convenient to use Ant tasks that have no direct equivalents, such as `<checksum>` and `<chown>`.
However, in the long term, it may be better to convert these to native Gradle task types that make use of standard Java APIs or third-party libraries.

+
.Declaring which projects are part of the build
====
include::sample[dir="snippets/mavenMigration/multiModule/kotlin",files="settings.gradle.kts"]
include::sample[dir="snippets/mavenMigration/multiModule/groovy",files="settings.gradle"]
====
<1> Sets the name of the overall project
<2> Configures two subprojects as part of this build
+
.Output of **`gradle projects`**
----