Hi Next my propositions for reporting Plugin Validation issues. Improve reporting [1] and documentation [2]
I see many benefits when we show "external" issues to users. Many times plugin authors don't care or don't know how to make theirs plugins better, ready for next Maven versions and so on When we also inform users about such issues I see that many plugins have fixed or will be fixed soon [3] without it I think that never will happen So we can think again if we should hide it by default, if someone doesn't like it can change on your system. [1] https://github.com/apache/maven/pull/1167 [2] https://github.com/apache/maven-site/pull/429 [3] https://github.com/search?q=maven.plugin.validation&type=issues https://github.com/search?q=maven.plugin.validation&type=pullrequests sob., 10 cze 2023 o 20:23 Henning Schmiedehausen <henn...@schmiedehausen.org> napisał(a): > On Fri, Jun 9, 2023 at 7:44 AM Slawomir Jaranowski <s.jaranow...@gmail.com > > > wrote: > > > In current 3.9.x we have: > > > > - NONE, // mute validation completely (validation issue collection still > > happens, it is just not reported!) > > - INLINE, // inline, each "internal" problem one line next to mojo > > invocation > > - SUMMARY, // at end, list of plugin GAVs along with "internal" issues > > - BRIEF, // synonym to SUMMARY > > - VERBOSE // at end, list of plugin GAVs along with detailed report of > ANY > > validation issues > > > > First BRIEF and SUMMARY are duplicated one should be enough. > > > > Then remove SUMMARY. We shipped BRIEF in Maven 3.9.2, so it is here to > stay. > > -h > -- Sławomir Jaranowski
