Hello colleagues,
I want to add a note about this. To me, this is a significant upgrade in
our macro capability. Previously developers had only two choices. They
could put individual macros in a template or create a global library of
macros available to all templates. Now, developers can creat
Hi list,
I'm really glad that I could solve both VELOCITY-362 and VELOCITY-529.
Here is a general description about how I solved the two problems.
These two problems are interrelated and solving one gives the chance
to solve the other as well. For example if we can specify that a set
of macro fil
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Velocity Wiki" for
change notification.
The following page has been changed by WillGlassHusain:
http://wiki.apache.org/jakarta-velocity/MacroIssues
The comment on the change is:
note that macro issues are fixed
---
[
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
[
https://issues.apache.org/jira/browse/VELOCITY-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Will Glass-Husain closed VELOCITY-529.
--
Resolution: Fixed
patch applied from VELOCITY-362. Nice work.
> Set a macro library
Thanks Nathan, that was exactly what I needed.
Nicholas
---
From "Nathan Bubna" <[EMAIL PROTECTED]>
Subject Re: Template.merge() doesn't throw ParseErrorException
Date Wed, 01 Aug 200
