[
https://issues.apache.org/jira/browse/MNG-7787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724598#comment-17724598
]
ASF GitHub Bot commented on MNG-7787:
-------------------------------------
rmannibucau commented on PR #1116:
URL: https://github.com/apache/maven/pull/1116#issuecomment-1556116622
@slawekjaranowski basic user interaction rule is to not show anything user
dont care or cant do anything to fix it so it is fully inacurrate as of today,
we'd better helo plugin dev with a live checker (ci/cd) and users with help
plugin. Doing it at build time with maven does not reach original goal nor is
relzvant since new versions will await user adoption (too late by design).
Let s provide the right tool and not bother users (n) instead lf dev (1).
> Introduce new options for plugin validation
> -------------------------------------------
>
> Key: MNG-7787
> URL: https://issues.apache.org/jira/browse/MNG-7787
> Project: Maven
> Issue Type: Improvement
> Components: Plugins and Lifecycle
> Affects Versions: 3.9.2
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 3.9.3, 4.0.0-alpha-6, 4.0.0
>
>
> Currently we offer following values for maven.plugin.validation:
> * BRIEF - emits one liner WARN with count of plugins having validation
> issues (IF count > 0)
> * DEFAULT - emits one line for each plugin GAV having validation issues
> * VERBOSE - emits detailed report for each plugin (declaration, use and
> problems) for each plugin having validation issue
> We should introduce more:
> * NONE - mute validation (usable on CI where plethora of WARNING lines could
> lead to falsely detect build as unhealthy)
> * INLINE - produce validation WARNs inline, as 3.9.1 did
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
