apache/maven · info

Fix reported issues by adjusting plugin configuration or by

Error message

Fix reported issues by adjusting plugin configuration or by upgrading above listed plugins. If no upgrade available, please notify plugin maintainers about reported issues.

What it means

The closing advice line of the VERBOSE plugin validation report. After listing all per-plugin findings, Maven tells you the two remedy paths: adjust the plugin configuration in your POM, or upgrade the listed plugins; if no upgrade exists, report the findings to the plugin maintainers. It is informational - the actual findings were printed above it.

Source

Thrown at impl/maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginValidationManager.java:270

                        for (IssueLocality issueLocality : issueLocalitiesToReport) {
                            Map<String, LinkedHashSet<String>> mojoIssues = issues.mojoIssues.get(issueLocality);
                            if (mojoIssues != null && !mojoIssues.isEmpty()) {
                                logger.warn("  Mojo {} issue(s):", issueLocality);
                                for (String mojoInfo : mojoIssues.keySet()) {
                                    logger.warn("   * Mojo {}", mojoInfo);
                                    for (String mojoIssue : mojoIssues.get(mojoInfo)) {
                                        logger.warn("     - {}", mojoIssue);
                                    }
                                }
                            }
                        }
                    }
                    logger.warn("");
                }
            }
            logger.warn("");
            if (validationReportLevel == ValidationReportLevel.VERBOSE) {
                logger.warn(
                        "Fix reported issues by adjusting plugin configuration or by upgrading above listed plugins. If no upgrade available, please notify plugin maintainers about reported issues.");
            }
            logger.warn(
                    "For more or less details, use 'maven.plugin.validation' property with one of the values (case insensitive): {}",
                    Arrays.toString(ValidationReportLevel.values()));
            logger.warn("");
        }
    }

    private boolean hasAnythingToReport(
            Map<String, PluginValidationIssues> issuesMap, EnumSet<IssueLocality> issueLocalitiesToReport) {
        for (PluginValidationIssues issues : issuesMap.values()) {
            if (hasAnythingToReport(issues, issueLocalitiesToReport)) {
                return true;
            }
        }
        return false;
    }

View on GitHub (pinned to e4093d4e12)

Solutions

1. Follow the advice literally: first try upgrading every plugin named in the report, then revisit remaining findings
2. For findings that survive the upgrade, file issues with the plugin maintainers attaching the report block
3. Adjust plugin configuration in your POM where the finding is about how the plugin is configured/declared

Example fix

// before: run with default reporting and ignore advice
mvn clean install
// after: let Maven propose current plugin versions, then upgrade them in pluginManagement
mvn versions:display-plugin-updates

mvn -q versions:display-plugin-updates  # act on the advice before it is printed: upgrade plugins

When it happens

Trigger: Any build that produced a VERBOSE validation report (validationReportLevel == VERBOSE) with at least one reportable issue; printed once at the end of the report block.

Common situations: Users seeing the report for the first time and unsure what to do next; triaging whether a finding is actionable locally (configuration) or upstream (plugin bug).

Related errors

• * {}
• Declared at location(s):
• * {}
• Plugin {} issue(s):
• Mojo {} issue(s):

AI-assisted analysis of apache/maven@e4093d4e12 (2026-08-21). Data as JSON: /api/errors/3dfdb5f93f27ff18. Report an issue: GitHub.