}

    @Override
    public String toString() {
        return "Report " + getName();
    }

    @Override
    public abstract FileSystemLocationProperty<? extends FileSystemLocation> getOutputLocation();

    @Deprecated
    @Override
    public void setDestination(File file) {
        DeprecationLogger.deprecateProperty(Report.class, "destination")
                .replaceWith("outputLocation")

        reporting.getReports().registerBinding(JacocoCoverageReport.class, DefaultJacocoCoverageReport.class);

        // Iterate and configure each user-specified report.
        reporting.getReports().withType(JacocoCoverageReport.class).all(report -> {
            report.getReportTask().configure(task -> {
                ArtifactView executionData = codeCoverageResultsConf.getIncoming().artifactView(view -> {

        reports.single().let { report ->
            assertThat(report.severity, equalTo(severity))
            assertThat(report.position, nullValue())
            assertThat(report.message, equalTo(message))
        }
    }

    fun assertSingleLineWarningReport(message: String, line: Int) {
        assertSingleEditorReport()
        reports.single().let { report ->

====

The `application` project requires no additional configuration if the `jvm-test-suite` plugin is present.

<1> Apply the `jacoco-report-aggregation` plugin
<2> Optional: make JaCoCo aggregate report generation part of the 'check' lifecycle phase

	match := dateRE.FindStringSubmatch(fname)
	if match == nil || len(match) < 2 {
		u.logger.Printf("Report name %q missing date", filepath.Base(fname))
	} else if match[1] > today {
		u.logger.Printf("Report date for %q is later than today (%s)", filepath.Base(fname), today)
		return // report is in the future, which shouldn't happen
	}
	buf, err := os.ReadFile(fname)
	if err != nil {

    }
}
// end::testtask-configuration[]

// tag::testtask-dependency[]
test {
    finalizedBy jacocoTestReport // report is always generated after tests run
}
jacocoTestReport {
    dependsOn test // tests are required to run before generating the report
}
// end::testtask-dependency[]

// tag::report-configuration[]
jacocoTestReport {
    reports {
        xml.required = false
        csv.required = false

import org.gradle.api.reporting.Report;
import org.gradle.api.reporting.ReportContainer;
import org.gradle.api.tasks.Internal;

/**
 * The reports produced by the {@link Test} task.
 */
public interface TestTaskReports extends ReportContainer<Report> {

    /**
     * A HTML report indicate the results of the test execution.
     *
     * @return The HTML report
     */
    @Internal

* `reporters/model-builder-plugin` shows how to use the Problems API to report problems when reading project configuration via the Tooling API.
* `reporters/script-plugin` shows how to use the Problems API in a precompiled script plugin.


## Emitting a problem

Problems can be emitted via an injected `Problems` service.
Here's an example on how to report a problem from a plugin.

====

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

https://github.com/checkstyle/contribution/tree/master/xsl[View a sample Checkstyle stylesheet.]

[[sec:enable_checkstyle_sarif]]
== Generate SARIF report

			}
		}
		buf.WriteString(p.msg)
	}
	return buf.String()
}

// report reports the error err, setting check.firstError if necessary.
func (err *error_) report() {
	if err.empty() {
		panic("no error")
	}

	// Cheap trick: Don't report errors with messages containing
	// "invalid operand" or "invalid type" as those tend to be