[
https://issues.apache.org/jira/browse/MNG-7811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17773066#comment-17773066
]
ASF GitHub Bot commented on MNG-7811:
-------------------------------------
hboutemy commented on code in PR #461:
URL: https://github.com/apache/maven-site/pull/461#discussion_r1349809583
##########
content/markdown/docs/3.9.5/release-notes.md:
##########
@@ -51,6 +51,7 @@ The full list of changes can be found in our [issue
management system][4].
* Mojos are prevented to bootstrap new instance of `RepositorySystem` (for
example by using deprecated `ServiceLocator`), they should reuse
`RepositorySystem` instance provided by Maven instead. See
[MNG-7471](https://issues.apache.org/jira/browse/MNG-7471).
* Each line in `.mvn/maven.config` is now interpreted as a single argument.
That is, if the file contains multiple arguments, these must now be placed on
separate lines, see [MNG-7684](https://issues.apache.org/jira/browse/MNG-7684).
* System and user properties handling cleanup, see
[MNG-7556](https://issues.apache.org/jira/browse/MNG-7556). As a consequence,
this may introduce breakage in environments where the user properties were used
to set system properties or other way around, for example see
[MNG-7887](https://issues.apache.org/jira/projects/MNG/issues/MNG-7887).
+* Plugins and extensions used by your build are checked against Maven
supported APIs and conventions: this "plugin validation" may report WARNINGs at
the end of your build. See [plugin validation
documentation](../../guides/plugins/validation/) to better understand what to
do when your build suffers from such warnings.
Review Comment:
done
> Plugins verification - reports are inconsistent
> -----------------------------------------------
>
> Key: MNG-7811
> URL: https://issues.apache.org/jira/browse/MNG-7811
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Reporter: Slawomir Jaranowski
> Assignee: Slawomir Jaranowski
> Priority: Major
> Fix For: 3.9.3, 4.0.0-alpha-7, 4.0.0
>
>
> We have report modes:
> {noformat}
> - 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
> {noformat}
> *NONE*
> - is ok works as expected, as documented
> *INLINE*
> - is ok works as expected, as documented
> *SUMMARY*, *BRIEF*
> - are the same - *{color:#ff0000}bug{color}*
> - prints *internal* issues in *VERBOSE* mode - *{color:#ff0000}bug{color}*
> *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 - *{color:#ff0000}bug{color}*
> h1. 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
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
