Author: andham Date: Mon Nov 7 21:58:40 2016 New Revision: 1768594 URL: http://svn.apache.org/viewvc?rev=1768594&view=rev Log: Fixed some site formatting errors
Modified: maven/plugins/trunk/maven-assembly-plugin/src/site/apt/advanced-module-set-topics.apt.vm Modified: maven/plugins/trunk/maven-assembly-plugin/src/site/apt/advanced-module-set-topics.apt.vm URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-assembly-plugin/src/site/apt/advanced-module-set-topics.apt.vm?rev=1768594&r1=1768593&r2=1768594&view=diff ============================================================================== --- maven/plugins/trunk/maven-assembly-plugin/src/site/apt/advanced-module-set-topics.apt.vm (original) +++ maven/plugins/trunk/maven-assembly-plugin/src/site/apt/advanced-module-set-topics.apt.vm Mon Nov 7 21:58:40 2016 @@ -128,9 +128,9 @@ ${module.groupId}-${module.artifactId}-$ Will result in a file called <<<org.test-project-1.0.jar>>> being created within the assembly. - <NOTE: The expression <<<$\{module.extension\}>>> is mapped to the file extension - supplied by the ArtifactHandler for the type <<<jar>>>. It's important to - remember that the file extension <<need not be .jar>>.> + <NOTE: The expression> <<<$\{module.extension\}>>> <is mapped to the file extension + supplied by the ArtifactHandler for the type> <<<jar>>>. <It's important to + remember that the file extension> <<need not be .jar>><.> * {Including Module Sources} @@ -362,7 +362,7 @@ ${module.groupId}-${module.artifactId}-$ * {Including Module Binaries} - *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. @@ -494,7 +494,7 @@ ${module.groupId}-${module.artifactId}-$ </assembly> --- - <NOTE: The <<<binaries>>> section still accommodates direct <<<\<includes/\>>>> - and <<<\<excludes/\>>>> subsections, for specifying which module-dependencies + <NOTE: The> <<<binaries>>> <section still accommodates direct> <<<\<includes/\>>>> + <and> <<<\<excludes/\>>>> <subsections, for specifying which module-dependencies to include in the assembly. However, these are deprecated, and only provided for backward compatibility.>