[maven-assembly-plugin] branch master updated: [MASSEMBLY-893] Typo in FAQ

[rf...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

rfscholte pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-assembly-plugin.git


The following commit(s) were added to refs/heads/master by this push:
     new 2ee29d1  [MASSEMBLY-893] Typo in FAQ
2ee29d1 is described below

commit 2ee29d169fae2d49dec6f730d9bfc09054b3767c
Author: Robert Scholte <rf...@apache.org>
AuthorDate: Fri Aug 3 10:04:31 2018 +0200

    [MASSEMBLY-893] Typo in FAQ
---
 src/site/fml/faq.fml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/site/fml/faq.fml b/src/site/fml/faq.fml
index cdf39f7..cc9cad2 100644
--- a/src/site/fml/faq.fml
+++ b/src/site/fml/faq.fml
@@ -99,7 +99,7 @@ under the License.
            to be adjusted or have the files they reference moved into the new child module alongside the descriptor itself.
         </p>
         <p>In cases where you absolutely must use module-binaries references, you should create an assembly-child POM mentioned above, then insert
-           <code>&lt;useAllReactorProjects&gt;true&lt;useAllReactorProjects&gt;</code> to each of your <code>moduleSet</code> sections. Then, bind the assembly
+           <code>&lt;useAllReactorProjects&gt;true&lt;/useAllReactorProjects&gt;</code> to each of your <code>moduleSet</code> sections. Then, bind the assembly
            in your assembly-child POM (normally to the <code>package</code> phase) using the <code>single</code> goal. When you execute the build from the top-level POM,
            Maven should generated your assembly in the new child project.
         </p>