This is an automated email from the ASF dual-hosted git repository.
hboutemy 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 4a1438f minor edits for clarification
4a1438f is described below
commit 4a1438f38c077569c5fdebeb04b526c8206c9d47
Author: jamesrwoodruff <jamesrwoodr...@gmail.com>
AuthorDate: Sun Nov 18 21:35:24 2018 -0800
minor edits for clarification
---
content/apt/guides/mini/guide-configuring-plugins.apt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/apt/guides/mini/guide-configuring-plugins.apt
b/content/apt/guides/mini/guide-configuring-plugins.apt
index 0b7be96..80fc31b 100644
--- a/content/apt/guides/mini/guide-configuring-plugins.apt
+++ b/content/apt/guides/mini/guide-configuring-plugins.apt
@@ -88,10 +88,10 @@ Guide to Configuring Plug-ins
[]
All plugins should have minimal required
- {{{/ref/current/maven-model/maven.html#class_plugin}informations}}:
+ {{{/ref/current/maven-model/maven.html#class_plugin}information}}:
<<<groupId>>>, <<<artifactId>>> and <<<version>>>.
- <<Important Note>>: It is recommended to always defined each version of the
plugins used by the build to guarantee
+ <<Important Note>>: It is recommended to always define each version of the
plugins used by the build to guarantee
the build reproducibility. A good practice is to specify them in the
<<<\<build\>\<pluginManagement/\>\</build\>>>>
elements for <<each>> build plugins (generally, you will define a
\<pluginManagement/\> element in a parent POM).
For reporting plugins, you should specify each version in the
<<<\<reporting\>\<plugins/\>\</reporting\>>>> elements
