You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by de...@apache.org on 2010/01/18 17:33:27 UTC

svn commit: r900452 - /maven/plugins/trunk/maven-assembly-plugin/src/site/apt/examples/multimodule/module-binary-inclusion-simple.apt.vm

Author: dennisl
Date: Mon Jan 18 16:33:27 2010
New Revision: 900452

URL: http://svn.apache.org/viewvc?rev=900452&view=rev
Log:
[MNGSITE-4] Fix broken link to FAQ entry

Modified:
    maven/plugins/trunk/maven-assembly-plugin/src/site/apt/examples/multimodule/module-binary-inclusion-simple.apt.vm

Modified: maven/plugins/trunk/maven-assembly-plugin/src/site/apt/examples/multimodule/module-binary-inclusion-simple.apt.vm
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-assembly-plugin/src/site/apt/examples/multimodule/module-binary-inclusion-simple.apt.vm?rev=900452&r1=900451&r2=900452&view=diff
==============================================================================
--- maven/plugins/trunk/maven-assembly-plugin/src/site/apt/examples/multimodule/module-binary-inclusion-simple.apt.vm (original)
+++ maven/plugins/trunk/maven-assembly-plugin/src/site/apt/examples/multimodule/module-binary-inclusion-simple.apt.vm Mon Jan 18 16:33:27 2010
@@ -30,10 +30,10 @@
 
 * Warning
 
-  *WARNING!* Using the <<<binaries>>> section of a <<<moduleSet>>> definition
+  <<Warning:>> Using the <<<binaries>>> section of a <<<moduleSet>>> definition
   involves some tricky considerations that are a result of the way Maven
   sorts and executes project builds within a multimodule context. Please
-  read {{{faq.html#module-binaries}this FAQ entry}} if you decide to use them.
+  read {{{../../faq.html#module-binaries}this FAQ entry}} if you decide to use them.
 
 * Introduction
 
@@ -139,7 +139,7 @@
   This will ensure that the output directory (normally, <<<target>>>), is
   removed before building the assembly directory. 
   
-  <<NOTE:>> Because of a quirk in Maven 2.0's execution model relating to 
+  <<Note:>> Because of a quirk in Maven 2.0's execution model relating to 
   aggregator mojos and the inheritance hierarchy, we need to explicitly execute 
   the package phase ahead of the assembly invocation, to ensure all modules have 
   been built.