[
https://issues.apache.org/jira/browse/MNG-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715673#comment-17715673
]
ASF GitHub Bot commented on MNG-7767:
-------------------------------------
cstamas commented on PR #1092:
URL: https://github.com/apache/maven/pull/1092#issuecomment-1519718672
IMHO this above IS aligned with my statement: "it changes output level ONLY
if value user passed is ANY of the 2 non-default values, otherwise is default"
In your case, it remained DEFAULT. Also, this property does not affect Maven
functionality (build, plugin or whatever wise), it merely controls the level of
output, I see no value of failing for invalid input (as in other case, it may
affect output of build, ie. making it incomplete or whatever... but again, this
property does not affect anything functionality wise, merely the report
detail). Validation happens "as early" as plugins are about to resolve, that is
already "late".
I really don't want to spread this all over the place just to achieve some
"ideal" state: i'd rather keep it simple and focused. To achieve early
validation, we need some early hook that would involve and perform validation,
etc... is it all really worth it? Again, this is really just a splat to user
face, to update the build. If he mistypes the property value, and instead of
"quiet" output "default" output happens, is it the end of the world? Should the
build break for it? Am unsure.
@slawekjaranowski @gnodet or anyone else? Any opinion?
> 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
> Assignee: 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)
