maven-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From micha...@apache.org
Subject [maven-site] 02/02: [MNGSITE-311] POM Reference: error in filter exemple description
Date Thu, 19 Jul 2018 21:37:12 GMT
This is an automated email from the ASF dual-hosted git repository.

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

commit e81e15a5e5aaf598c97e37790a2bd5945435363c
Author: Michael Osipov <michaelo@apache.org>
AuthorDate: Thu Jul 19 23:36:39 2018 +0200

    [MNGSITE-311] POM Reference: error in filter exemple description
---
 content/apt/pom.apt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/apt/pom.apt b/content/apt/pom.apt
index 8119e92..3120f78 100644
--- a/content/apt/pom.apt
+++ b/content/apt/pom.apt
@@ -897,7 +897,7 @@ Display parameters as parsed by Maven (in canonical form) and comparison
result:
   Defines <<<*.properties>>> files that contain a list of properties that
apply to resources which
   accept their settings (covered below). In other words, the "<<<name=value>>>"
pairs defined within
   the filter files replace <<<$\{name\}>>> strings within resources on
build. The example above defines
-  the <<<filter1.properties>>> file under the <<<filter/>>>
directory. Maven's default filter
+  the <<<filter1.properties>>> file under the <<<filters/>>>
directory. Maven's default filter
   directory is <<<$\{basedir\}/src/main/filters/>>>.
 
   For a more comprehensive look at what filters are and what they can do, take a look at
the


Mime
View raw message