Author: andham
Date: Mon May 16 19:43:45 2016
New Revision: 1744118

URL: http://svn.apache.org/viewvc?rev=1744118&view=rev
Log:
Minor change to wording as well as fixed a visual escaping glitch

Modified:
    
maven/plugins/trunk/maven-resources-plugin/src/site/apt/examples/encoding.apt.vm

Modified: 
maven/plugins/trunk/maven-resources-plugin/src/site/apt/examples/encoding.apt.vm
URL: 
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-resources-plugin/src/site/apt/examples/encoding.apt.vm?rev=1744118&r1=1744117&r2=1744118&view=diff
==============================================================================
--- 
maven/plugins/trunk/maven-resources-plugin/src/site/apt/examples/encoding.apt.vm
 (original)
+++ 
maven/plugins/trunk/maven-resources-plugin/src/site/apt/examples/encoding.apt.vm
 Mon May 16 19:43:45 2016
@@ -32,9 +32,9 @@ Specifying a character encoding scheme
  A character encoding scheme such as <<<ASCII>>>, <<<UTF-8>>> or <<<UTF-16>>> 
can be chosen to be
  used for the reading and writing of files.
 
- The best practice is to define 
{{{https://maven.apache.org/general.html#encoding-warning}encoding}} for copying
- files via the property <<<${project.build.sourceEncoding}>>> which should be 
defined in the pom
- properties section like this:
+ The best practice is to 
{{{https://maven.apache.org/general.html#encoding-warning}define encoding}}
+ for copying filtered resources via the property 
<<<$\{project.build.sourceEncoding}>>> which should be
+ defined in the pom properties section like this:
  
 +-----+
 <project ...>


Reply via email to