Tapestry 5
  1. Tapestry 5
  2. TAP5-346

Maven resource filtering pre-expands some Tapestry expansions: docs should warn of this

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 5.0.15
    • Fix Version/s: 5.1.0.0
    • Component/s: documentation
    • Labels:
      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>

        Activity

        Franz Amador created issue -
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Assignee Howard M. Lewis Ship [ hlship ]
        Howard M. Lewis Ship made changes -
        Fix Version/s 5.1.0.0 [ 12313428 ]
        Resolution Fixed [ 1 ]
        Status Open [ 1 ] Closed [ 6 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Closed Closed
        74d 6h 1 Howard M. Lewis Ship 24/Jan/09 01:17

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Franz Amador
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development