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 SaileshChintada: http://wiki.apache.org/jakarta-velocity/MacroIssues The comment on the change is: Updated the 2 links to a working ones ------------------------------------------------------------------------------ Most of these issues stem from how Velocity stores macros. Macros can be stored either at a global level or on a per-template level. This is controlled by the config key "velocimacro.permissions.allow.inline.local.scope", which is false by default. (i.e. all macros are part of global scope). See the - [http://jakarta.apache.org/velocity/docs/developer-guide.html#Velocity%20Configuration%20Keys%20and%20Values developer's guide]. + [http://velocity.apache.org/engine/devel/developer-guide.html#velocity_configuration_keys_and_values developer's guide]. This means that the following common-sense use case (referenced in VELOCITY-277, VELOCITY-362, and VELOCITY-136) just doesn't work. @@ -51, +51 @@ but is impractical in practice for the following reasons. * First of all, it doesn't work. Hence the first three bugs. They are technically not bugs since this behavior is - [http://jakarta.apache.org/velocity/docs/user-guide.html#Velocimacro%20Miscellany documented], though that's difficult to find. + [http://velocity.apache.org/engine/devel/user-guide.html#velocimacro_miscellany documented], though that's difficult to find. * Currently macros are evaluated at parse time while #parse is evaluated at runtime. (allowing the template to dynamically choose a page to include). That's why the macro is not picked up by the #parse. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
