[
https://issues.apache.org/jira/browse/MNG-7787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724400#comment-17724400
]
ASF GitHub Bot commented on MNG-7787:
-------------------------------------
cstamas commented on PR #1116:
URL: https://github.com/apache/maven/pull/1116#issuecomment-1555194878
-1 since, as nicely said on ML, it "defies the purpose".
Stick to 3.8.x, if this is no go for you for any reason.
Goal is to fix issues all way down the pipe (like use of broken
maven-plugin-plugin), and yes, not all core plugins are fixed, yet. Give us a
bit more time, or hop in, never enough help in this area.
> 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: 4.0.0-alpha-6, 4.0.0, 3.9.3
>
>
> 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)
