[ 
https://issues.apache.org/jira/browse/MSITE-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177575#comment-15177575
 ] 

Michael Osipov commented on MSITE-768:
--------------------------------------

Christian, it was not documented to work anyway. You realied on an unsupported 
broken feature. Let's make it work for everyone. To fix this, it takes several 
other issues first which are easy to address.

> maven-site-plugin 3.5 breaks Velocity #parse and #include
> ---------------------------------------------------------
>
>                 Key: MSITE-768
>                 URL: https://issues.apache.org/jira/browse/MSITE-768
>             Project: Maven Site Plugin
>          Issue Type: Bug
>    Affects Versions: 3.5
>         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"
>            Reporter: Christian Schlichtherle
>            Priority: Blocker
>         Attachments: msite-768.zip
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to