Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
5.0.15
-
None
Description
If Maven resource filtering is turned on in the pom.xml file, Maven will evaluate any Tapestry expansions that match properties in the pom.xml file. For example, the string "${name}" in my component .tml files was being expanded to the value of the name property in my pom.xml file. Utterly baffling until I found the explanation on Nabble. It would be very helpful to add a note about this in the sections of the docs that cover expansions. Even better would be to show the solution, which is to add an "excludes" block to the pom.xml, like this:
<resource>
<directory>src/main/resources</directory>
<excludes>
<exclude>*/.tml</exclude>
</excludes>
<filtering>true</filtering>
</resource>