[MSITE-768] Support Velocity's #parse and #include

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.5
• Fix Version/s: 3.5.1

Environment

$ 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"

• Assignee: Michael Osipov
• Reporter: Christian Schlichtherle
• Created: 28/Feb/16 21:13
• Updated: 10/Apr/16 11:47
• Resolved: 10/Apr/16 10:56

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.

Issue Links

• depends upon: DOXIASITETOOLS-157 Add support for Velocity #parse and #include with relative paths
• is related to: DOXIASITETOOLS-144 Split default-site.vm into 2 parts: default-site.vm and default-site-macros.vm
• links to: Best source ever