From e56bf0e96a4f99514cbeb16798fb7f45d2168c30 Mon Sep 17 00:00:00 2001 From: Bruno Borges Date: Tue, 7 Jul 2026 13:54:12 -0400 Subject: [PATCH] Clarify Java problem matcher annotations Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- docs/advanced-usage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/advanced-usage.md b/docs/advanced-usage.md index 16ae592d..65193c4b 100644 --- a/docs/advanced-usage.md +++ b/docs/advanced-usage.md @@ -608,7 +608,7 @@ jobs: `setup-java` registers a [problem matcher](https://github.com/actions/toolkit/blob/main/docs/problem-matchers.md) for Java after installing the JDK. It scans the log output of subsequent steps and turns `javac` diagnostics into GitHub [annotations](https://docs.github.com/actions/using-workflows/workflow-commands-for-github-actions#setting-a-warning-message) that appear in the run summary and inline on the affected files. It matches two kinds of lines: - Compiler errors and warnings, e.g. `App.java:12: error: cannot find symbol` (owner `javac`). -- Uncaught exception stack traces, e.g. `Exception in thread "main" ...` (owner `java`). +- Uncaught-exception header lines, e.g. `Exception in thread "main" ...`; because these lines have no file or line captures, they appear as log/run-level annotations rather than inline file annotations (owner `java`). This is enabled by default and requires no configuration.