[ https://issues.apache.org/jira/browse/VELOCITY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521848 ]
Will Glass-Husain commented on VELOCITY-362: -------------------------------------------- Patch applied. I refactored the tests a bit to test all 4 combinations of cache on/off and local/global macro namespace. the tests also check that if you change the #parse'd file, the macro definitions change. I'm going to leave this issue open -- there's a few changes to the docs that are needed. We can close the issue once the docs are updated. > 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 > > > 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]