[
https://issues.apache.org/jira/browse/VELOCITY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated VELOCITY-362:
-----------------------------------------
Attachment: small.patch
There is a lack of a feature in the code due to a small mistake. That
was when a user includes two macro libraries via the #parse directive,
if the libraries contain the same macro, the library included later
should take precedence. But it was not supported and it was due to a
very simple mistake (for loop counting upwards instead downwards). I
have corrected this and attached a patch containing the changes.
> can't load macros in file loaded with #parse
> --------------------------------------------
>
> Key: VELOCITY-362
> URL: https://issues.apache.org/jira/browse/VELOCITY-362
> Project: Velocity
> Issue Type: Improvement
> Components: Engine
> Affects Versions: 1.4
> Environment: Operating System: All
> Platform: All
> Reporter: whxbb
> Priority: Minor
> Fix For: 1.6
>
> Attachments: patch.zip, small.patch
>
>
> I think this is a big bug. I've used velocity in my projects, erveything is ok
> but this. i want to know it's this problem will be resolved in next version?
> if
> it's not, i have to abandon velocity.
> the bug is :
> from doc:
> 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.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
