You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Will Glass-Husain (JIRA)" <de...@velocity.apache.org> on 2008/07/14 07:27:32 UTC
[jira] Commented: (VELOCITY-604) Allow definition of macro's within
parsed files
[ https://issues.apache.org/jira/browse/VELOCITY-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613244#action_12613244 ]
Will Glass-Husain commented on VELOCITY-604:
--------------------------------------------
Thanks, Paul. This is fixed in the forthcoming version 1.6. You can download from svn head and try it out.
I'm changing this issue to note we need to fix the docs.
> Allow definition of macro's within parsed files
> -----------------------------------------------
>
> Key: VELOCITY-604
> URL: https://issues.apache.org/jira/browse/VELOCITY-604
> Project: Velocity
> Issue Type: Improvement
> Components: Engine
> Affects Versions: 1.4, 1.5
> Reporter: Paul Curren
>
> Your documentation at http://velocity.apache.org/engine/releases/velocity-1.5/user-guide.html#velocimacro_miscellany has the following snippet -
> "
> Velocimacro Trivia
> -------------------------
> Currently, Velocimacros must be defined before they are first used in a template. This means that your #macro() declarations should come before using the Velocimacros.
> This is important to remember if you try to #parse() a template containing inline #macro() directives. Because the #parse() happens at runtime, and the parser decides if a VM-looking element in the template is a VM at parsetime, #parse()-ing a set of VM declarations won't work as expected. To get around this, simply use the velocimacro.library facility to have Velocity load your VMs at startup.
> Is this likely to change in any forthcoming versions?
> The use case is theme development for Confluence. It would be nice to be able to share some common macro definitions between a number of templates within a theme (i.e. not inlining). And using the velocimacro.library property isn't really an option because themes are dynamically loaded or unloaded.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org