[
https://issues.apache.org/jira/browse/MNG-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713090#comment-17713090
]
ASF GitHub Bot commented on MNG-7767:
-------------------------------------
cstamas commented on PR #1092:
URL: https://github.com/apache/maven/pull/1092#issuecomment-1511340493
> I am really confused why `RepositorySystemSession` and `ConfigUtils` are
used here. They feel a bit misplaced in plugin validation, don't they?
Well, this PR does not change anything about that. But, as validation is per
session, the session is really the only thing that offers itself to store
things in "natural" way. MavenSession does not have any means for this, so it
is resolver session data that is used. It is done like it as this guarantees
that validator does do what it needs to do in correct way in single-threaded
and multi-threaded mvn and also in mvnd.
> Tone down plugin validation report
> ----------------------------------
>
> Key: MNG-7767
> URL: https://issues.apache.org/jira/browse/MNG-7767
> Project: Maven
> Issue Type: Improvement
> Components: Plugins and Lifecycle
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 3.9.2, 4.0.0-alpha-6, 4.0.0
>
>
> Tone down the plugin validation (current "default" output for Maven build
> even emits 1.5 screens of warning):
> [https://gist.github.com/cstamas/02d6fd3e969efe4a17186504b355c080#file-gistfile1-txt-L25]
> I'd change it like:
> * DISABLED mode emits one line (as today)}
> * NORMAL mode would emit something like this
> [https://gist.github.com/cstamas/10765b9e697e5605124bd65fd9cdafca]
> * VERBOSE mode emits full report (as today)
> At the same time, rename the "modes" as current mode names does not reflect
> what they do:
> * disabled -> brief (emits one liner warning)
> * normal -> default (emits list of plugins)
> * verbose -> verbose (emits full report)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
