[
https://issues.apache.org/jira/browse/MNG-7787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724602#comment-17724602
]
ASF GitHub Bot commented on MNG-7787:
-------------------------------------
rmannibucau commented on PR #1116:
URL: https://github.com/apache/maven/pull/1116#issuecomment-1556127323
@slawekjaranowski a misconfiguration should be reported indeed, but the
point is: why at each run? it is a static analyzis thing and should either be
done at request (help:validate-project for ex) and then forgotten cause if user
intend this usage (some deprecation have no replacement and are intended to be
used temporarly). So for me we address a very good usage but with a wrong
solution.
> 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)
