Somehow, during site generation, the </> entities got filtered
out, thus the pom.xml example doesn't contain the <> signs around the
xml tags. Indentation would be nice, too.
Uli
Howard M. Lewis Ship (JIRA) schrieb:
[
https://issues.apache.org/jira/browse/TAP5-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAP5-346.
-------------------------------------
Resolution: Fixed
Fix Version/s: 5.1.0.0
Maven resource filtering pre-expands some Tapestry expansions: docs should warn
of this
---------------------------------------------------------------------------------------
Key: TAP5-346
URL: https://issues.apache.org/jira/browse/TAP5-346
Project: Tapestry 5
Issue Type: Improvement
Components: documentation
Affects Versions: 5.0.15
Reporter: Franz Amador
Assignee: Howard M. Lewis Ship
Priority: Minor
Fix For: 5.1.0.0
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>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
