[
https://issues.apache.org/jira/browse/MNG-7787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724426#comment-17724426
]
ASF GitHub Bot commented on MNG-7787:
-------------------------------------
hgschmie commented on PR #1116:
URL: https://github.com/apache/maven/pull/1116#issuecomment-1555302832
I very much disagree with your "my way or the highway" approach. There is a
lot of criticism with the approach to "the purpose". Of course, you can just
ram your approach through and hope for the best. It will not work, as the
changes *will* break older builds that people do not update and you cause
continuing pain for developers. People will be stuck on 3.9 forever because "it
is the last version that supports that unmaintained foo plugin that I need for
my build and can not move off" and grind their teeth. The answer will be "we
move off maven", not "we fix that plugin".
> 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)
