You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2023/05/19 12:19:00 UTC

[jira] [Commented] (MNG-7787) Introduce new options for plugin validation

    [ https://issues.apache.org/jira/browse/MNG-7787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724240#comment-17724240 ] 

Slawomir Jaranowski commented on MNG-7787:
------------------------------------------

Something between DEFAULT and VERBOSE will be useful, list plugin and problems but without locations.


> 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
>            Priority: Major
>             Fix For: 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)