Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
We have report modes:
- 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
NONE
- is ok works as expected, as documented
INLINE
- is ok works as expected, as documented
SUMMARY, BRIEF
- are the same - bug
- prints internal issues in VERBOSE mode - bug
VERBOSE
- is ok works as expected, as documented
So we don't have possibility to report an external issues in brief mode - as a list at the end, also - bug
Proposition
- SUMMARY - prints internal and external issues as list at the end
- BRIEF - prints internal issues in INLINE and external as list at the end
- prepare documentation on Maven site with explanation of common issues and what user can do with it
Attachments
Issue Links
- is related to
-
MNG-7786 Maven Plugin Validation message is misleading
- Closed
-
MNG-7787 Introduce new options for plugin validation
- Closed
-
MNG-7788 Plugin Validation Report should be printed before build summary
- Closed
- relates to
-
MNG-5222 Maven 3 no longer logs warnings about deprecated plugin parameters.
- Closed
-
MNG-7457 Warn about deprecated plugin Mojo
- Closed
-
MNG-7464 Warn about using read-only parameters for Mojo in configuration
- Closed
-
MNG-7706 Deprecate ${localRepository} mojo parameter expression
- Closed
-
MNG-7712 Core should issue a warning if plugin depends on maven-compat
- Closed
- links to