You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2013/01/13 21:24:13 UTC
[jira] (DOXIASITETOOLS-78) Velocity's ContextTool fails to
configure
Michael Osipov created DOXIASITETOOLS-78:
--------------------------------------------
Summary: Velocity's ContextTool fails to configure
Key: DOXIASITETOOLS-78
URL: https://jira.codehaus.org/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
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIASITETOOLS-78) Velocity's ContextTool fails to
configure
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/DOXIASITETOOLS-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed DOXIASITETOOLS-78.
----------------------------------------
Resolution: Duplicate
Assignee: Robert Scholte
Considering this as a duplicate of DOXIASITETOOLS-67. Standalone it works fine (there are unit-tests confirming this), but once classloaders get involved, the wrong one is picked up.
> Velocity's ContextTool fails to configure
> -----------------------------------------
>
> Key: DOXIASITETOOLS-78
> URL: https://jira.codehaus.org/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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira