[MWAR-164] Support for specifying which encoding to use when filtering resources
- Add more documentation.
git-svn-id: https://svn.apache.org/repos/asf/maven/plugins/trunk@1391312 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/src/site/apt/examples/adding-filtering-webresources.apt.vm b/src/site/apt/examples/adding-filtering-webresources.apt.vm
index e7a037d..a4253f6 100644
--- a/src/site/apt/examples/adding-filtering-webresources.apt.vm
+++ b/src/site/apt/examples/adding-filtering-webresources.apt.vm
@@ -2,8 +2,9 @@
Adding and Filtering External Web Resources
------
Pete Marvin King
+ Dennis Lundberg
------
- 2012-09-25
+ 2012-09-28
------
~~ Licensed to the Apache Software Foundation (ASF) under one
@@ -341,6 +342,14 @@
</another_ioc_container>
+----------+
+ <<Note:>> In versions 2.2 and earlier of this plugin the platform encoding was
+ used when filtering resources. Depending on what that encoding was you could
+ end up with scrambled characters after filtering. Starting with version 2.3
+ this plugin respects the property <<<project.build.sourceEncoding>>> when
+ filtering resources. One notable exception to this is that <<<.xml>>> files
+ are filtered using the encoding specified inside the xml-file itself.
+
+
**Overriding the default destination directory
By default web resources are copied to the root of the WAR, as shown in the previous example.
