Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Duplicate
-
1.3
-
None
-
None
-
Maven 2.2.1, Maven Site Plugin 3.2
Description
The newly introduced ToolManager creates an unusable ContextTool.
I have defined this property in pom.xml/project/properties section:
<maven.compiler.target>1.6</maven.compiler.target>
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.
Attachments
Attachments
Issue Links
- duplicates
-
DOXIASITETOOLS-93 request-scoped default Velocity Tools are not accessible
- Closed