[jira] [Commented] (DOXIASITETOOLS-78) Velocity's ContextTool fails to configure

["Michael Osipov (JIRA)" <ji...@apache.org>]

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

Michael Osipov commented on DOXIASITETOOLS-78:
----------------------------------------------

This is rather a duplciate of DOXIASITETOOLS-93 because the {{ToolManager}} works in general.

> Velocity's ContextTool fails to configure
> -----------------------------------------
>
>                 Key: DOXIASITETOOLS-78
>                 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-78
>             Project: Maven Doxia Sitetools
>          Issue Type: Bug
>          Components: Doc renderer
>    Affects Versions: 1.3
>         Environment: Maven 2.2.1, Maven Site Plugin 3.2
>            Reporter: Michael Osipov
>            Assignee: Robert Scholte
>            Priority: Critical
>         Attachments: Velocity merge exception.png
>
>
> The newly introduced ToolManager creates an unusable {{ContextTool}}.
> I have defined this property in {{pom.xml/project/properties}} section:
> {code:xml}
> <maven.compiler.target>1.6</maven.compiler.target>
> {code}
> As per doc, all properties are available in the Velocity context. It simply does not matter whether you say {{$context}} or {{$context.get("...")}} in your apt.vm template, it fails with runtime exception from {{velocity.getEngine().mergeTemplate( resource, siteContext.getInputEncoding(), vc, sw );}}
> See attached screenshot.



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