Fix #12643: Migrate PluginValidationManager to native BuilderProblem API Change the PluginValidationManager interface from String-based to BuilderProblem-based, enabling structured problem reporting with keys, severity, and suggestions throughout the plugin validation pipeline. - Change 3 abstract report methods from String issue to BuilderProblem - Add deprecated String-based default methods for backward compat - Update all 9 call sites (7 validators + 1 plugin manager) to create BuilderProblem with structured key, severity, and suggestion - Inject DefaultDiagnosticCollector into DefaultPluginValidationManager to pipe problems into the diagnostic pipeline - Add japicmp exclusion for the intentional API break - Add DefaultPluginValidationManager to EXCLUDED_LOGGERS in BuildReportCollector to prevent double-counting Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Apache Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting and documentation from a central piece of information.
If you think you have found a bug, please file an issue in the Maven Issue Tracker.
More information can be found on Apache Maven Homepage. Questions related to the usage of Maven should be posted on the Maven User List.
You can download the release source from our download page.
If you are interested in the development of Maven, please consult the documentation first and afterward you are welcome to join the developers mailing list to ask questions or discuss new ideas/features/bugs etc.
Take a look into the contribution guidelines.
This code is under the Apache License, Version 2.0, January 2004.
See the NOTICE file for required notices and attributions.
Do you like Apache Maven? Then donate back to the ASF to support the development.
If you want to bootstrap Maven, you'll need:
mvn -DdistributionTargetDir="$HOME/app/maven/apache-maven-4.1.x-SNAPSHOT" clean package
