The GitHub Actions job "CodeQL" on grails-intellij-plugin.git/intellij-ce-support has succeeded. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: c338a0905cebeff88f41a67e4e35e70150801b73 / James Daugherty <[email protected]> Make JaCoCo see the plugin classes the tests actually run Codecov has reported 0% for the whole project because the coverage data never contained a single plugin class. Two JaCoCo defaults are wrong for an IntelliJ plugin, and either one alone yields 0% for every class rather than an error: - The tests load the plugin from the sandbox jars, which IPGP builds from the instrumented classes (instrumentCode adds the @NotNull assertions). JaCoCo keys execution data by class identity, so a report analysing build/classes matches nothing. The per-project reports and the root aggregate now analyse build/instrumented/instrumentCode where that task exists, and the plain classes elsewhere. - IntelliJ's plugin class loaders define classes without a code-source location, which the JaCoCo agent skips by default; the exec file held only the Gradle test-worker classes. The Test tasks now set includeNoLocationClasses, excluding jdk.internal.* as JaCoCo recommends. The three new content modules join the aggregate, and AGENTS.md records both settings. With the full suite the aggregate now reports 60% line coverage. Report URL: https://github.com/apache/grails-intellij-plugin/actions/runs/36816844496 With regards, GitHub Actions via GitBox
