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
Priority: Minor
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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
