This is an automated email from the ASF dual-hosted git repository.
sjaranowski pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git
The following commit(s) were added to refs/heads/master by this push:
new 5dce6c07 Add documentation for maven.plugin.validation.excludes
5dce6c07 is described below
commit 5dce6c07457dfdb12875bd3fafe68a7629678a7c
Author: Slawomir Jaranowski <s.jaranow...@gmail.com>
AuthorDate: Sun Apr 14 18:48:04 2024 +0200
Add documentation for maven.plugin.validation.excludes
- https://issues.apache.org/jira/browse/MNG-7939
---
content/markdown/guides/plugins/validation/index.md | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/content/markdown/guides/plugins/validation/index.md
b/content/markdown/guides/plugins/validation/index.md
index 757d5d64..573b7759 100644
--- a/content/markdown/guides/plugins/validation/index.md
+++ b/content/markdown/guides/plugins/validation/index.md
@@ -54,6 +54,18 @@ External Plugins issues require to be fixed by plugin
authors first.
In such cases users can try to update plugin to newer version.
If the newest version of plugin still has such an issue, users should report
problem to plugin authors.
+## Exclude plugins from validation
+
+In some case we know about issues in some plugin and we want exclude it from
validation.
+We can do it by property `maven.plugin.validation.excludes`, eg:
+
+```
+mvn
-Dmaven.plugin.validation.excludes=plugin1-goupId:plugin1-artifactId:plugin1-version,plugin2-goupId:plugin2-artifactId:plugin2-version
+```
+
+Property `maven.plugin.validation` has tha same rule as
`maven.plugin.validation` - can only be used on command line (not as property
in POM)
+
+
## Manage Plugin Validation verbosity
In order to manage Plugin Validation verbosity, a Maven user property
`-Dmaven.plugin.validation=...` can be used on command line (or injected: see
below).
