* Run the build and view the test report
* Customize the Jar files the build produces

Now you could complete this exercise by trying to compile some ${language.raw} code that uses the library you just built.

== Next steps

Building a library is just one aspect of reusing code across project boundaries.
From here, you may be interested in:

 - link:{userManualPath}/building_java_projects.html[Building Java & JVM projects]

				capitalize = false
			} else {
				buffer.WriteRune(r)
			}
		} else {
			capitalize = true
		}
	}
	return buffer.String()
}

// GetOperationIDAndTags returns a customize operation ID and a list of tags for kubernetes API server's OpenAPI spec to prevent duplicate IDs.
func GetOperationIDAndTags(r *restful.Route) (string, []string, error) {
	op := r.Operation
	path := r.Path
	var tags []string

due to design choices in Helm.
The underlying Kubernetes resources we configure have 1000s of fields; given enough users and bespoke use cases,
eventually someone will want to customize every one of those fields.
If all fields are exposed in `values.yaml`, we end up with an massive API that is also likely worse than just using the Kubernetes API directly.

* Run the build and view the test report
* Execute a ${language.raw} application using the `run` task from the `application` plugin
* Bundle the application in an archive

== Next steps

To learn more about how you can further customize ${language.raw} application projects, check out the following user manual chapters:

 - link:{userManualPath}/building_java_projects.html[Building Java & JVM projects]

        task.reports.enabled*.name == ["html"]
        task.reports.html.outputLocation.asFile.get() == project.file("build/reports/codenarc/custom.html")
        task.ignoreFailures == false
    }

    def "can customize additional tasks via extension"() {
        def task = project.tasks.create("codenarcCustom", CodeNarc)

        project.codenarc {
            config = project.resources.text.fromFile("codenarc-config")

|===

[[sec:pmd_configuration]]
== Configuration

====
include::sample[dir="snippets/codeQuality/codeQuality/kotlin",files="build.gradle.kts[tags=customize-pmd]"]
include::sample[dir="snippets/codeQuality/codeQuality/groovy",files="build.gradle[tags=customize-pmd]"]
====

See the link:{groovyDslPath}/org.gradle.api.plugins.quality.PmdExtension.html[PmdExtension] class in the API documentation.

[[sec:pmd_conf_threads]]

apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
metadata:
  namespace: istio-system
spec:
  profile: default
  meshConfig:
    trustDomain: example.org
  values:
    global:
    # This is used to customize the sidecar template
    sidecarInjectorWebhook:
      templates:
        spire: |
          spec:
            containers:
            - name: istio-proxy
              volumeMounts:

 * limitations under the License.
 */

package org.gradle.caching.http.internal;

import org.apache.http.HttpRequest;

@FunctionalInterface
public interface HttpBuildCacheRequestCustomizer {
    void customize(HttpRequest request);

COPY --from=distroless_source /home/nonroot /home/nonroot
RUN echo istio-proxy:x:1337: >> /home/etc/group
RUN echo istio-proxy:x:1337:1337:istio-proxy:/nonexistent:/sbin/nologin >> /home/etc/passwd

# Customize distroless with the following:
# - password file
# - groups file
# - /home/nonroot directory
FROM distroless_source
COPY --from=ubuntu_source /home/etc/passwd /etc/passwd

class ProjectHierarchyCustomizationIntegrationTest extends AbstractIntegrationSpec {
    @Issue("https://github.com/gradle/gradle/issues/18726")
    @ToBeFixedForConfigurationCache(skip = INVESTIGATE)
    def "can customize name of child project before customizing the name of parent project"() {
        createDirs("modules", "modules/projectA", "modules/projectA/projectB")
        settingsFile << """
            include("modules:projectA:projectB")