Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.5
-
None
-
None
-
$ mvn --version
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
Maven home: /usr/local/Cellar/maven/3.3.9/libexec
Java version: 1.8.0_74, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "10.11.3", arch: "x86_64", family: "mac"
$ mvn --version Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00) Maven home: /usr/local/Cellar/maven/3.3.9/libexec Java version: 1.8.0_74, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/jre Default locale: de_DE, platform encoding: UTF-8 OS name: "mac os x", version: "10.11.3", arch: "x86_64", family: "mac"
Description
It seem like since version 3.5, I cannot use #parse or #include in Velocity filtered templates anymore. See attached test project.
Please note that it doesn't matter what the name of the file to parse is. You can even change it to a non-existent file (e.g. "foo") and it all still abort unnecessary recursion.
Attachments
Attachments
Issue Links
- depends upon
-
DOXIASITETOOLS-157 Add support for Velocity #parse and #include with relative paths
- Closed
- is related to
-
DOXIASITETOOLS-144 Split default-site.vm into 2 parts: default-site.vm and default-site-macros.vm
- Closed
- links to