You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Christoph Reck (JIRA)" <de...@velocity.apache.org> on 2007/04/24 17:56:15 UTC
[jira] Created: (VELOCITY-540) Make local directive part of
Velocity engine core
Make local directive part of Velocity engine core
-------------------------------------------------
Key: VELOCITY-540
URL: https://issues.apache.org/jira/browse/VELOCITY-540
Project: Velocity
Issue Type: Wish
Components: Engine
Reporter: Christoph Reck
I prefer #local vs velocimacro.context.localscope because
you can create macro libraries that allow declaring local vars
without polluting the namespace, but also enables setting global
variables. See the thread ending on 16.04.2007 "RE: velocimacro.context.localscope"
with the #springBind example for such a case.
If #local is not part of the core, it cannot be used for general purpose velocity macro libraries...
--
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
[jira] Commented: (VELOCITY-540) Make local directive part of
Velocity engine core
Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681380#action_12681380 ]
Nathan Bubna commented on VELOCITY-540:
---------------------------------------
I should note that the $macro namespace was added via VELOCITY-704.
> Make local directive part of Velocity engine core
> -------------------------------------------------
>
> Key: VELOCITY-540
> URL: https://issues.apache.org/jira/browse/VELOCITY-540
> Project: Velocity
> Issue Type: Wish
> Components: Engine
> Reporter: Christoph Reck
> Fix For: 1.7, 2.0
>
>
> I prefer #local vs velocimacro.context.localscope because
> you can create macro libraries that allow declaring local vars
> without polluting the namespace, but also enables setting global
> variables. See the thread ending on 16.04.2007 "RE: velocimacro.context.localscope"
> with the #springBind example for such a case.
> If #local is not part of the core, it cannot be used for general purpose velocity macro libraries...
--
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
[jira] Resolved: (VELOCITY-540) Make local directive part of
Velocity engine core
Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Bubna resolved VELOCITY-540.
-----------------------------------
Resolution: Won't Fix
Fix Version/s: 2.0
1.7
With the addition of the $macro namespace in 1.7 and 2.0, you can now easily create macros that will not affect the parent context. velocimacro.context.localscope and #local are both unnecessary.
> Make local directive part of Velocity engine core
> -------------------------------------------------
>
> Key: VELOCITY-540
> URL: https://issues.apache.org/jira/browse/VELOCITY-540
> Project: Velocity
> Issue Type: Wish
> Components: Engine
> Reporter: Christoph Reck
> Fix For: 1.7, 2.0
>
>
> I prefer #local vs velocimacro.context.localscope because
> you can create macro libraries that allow declaring local vars
> without polluting the namespace, but also enables setting global
> variables. See the thread ending on 16.04.2007 "RE: velocimacro.context.localscope"
> with the #springBind example for such a case.
> If #local is not part of the core, it cannot be used for general purpose velocity macro libraries...
--
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