[jira] Commented: (VELOCITY-704) VTL Simplicity - Control objects

[ https://issues.apache.org/jira/browse/VELOCITY-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681178#action_12681178 ] Nathan Bubna commented on VELOCITY-704: --- Ok, i think that should do it code-wise.

[GUMP@vmgump]: Project velocity-engine (in module velocity-engine) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project velocity-engine has an issue affecting its community integration. This

[jira] Resolved: (VELOCITY-680) RFC: New #local directive that behaves like #set but puts things into local context in macro rendering

[ https://issues.apache.org/jira/browse/VELOCITY-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Bubna resolved VELOCITY-680. --- Resolution: Won't Fix This has been obviated by the deprecation/removal of

[jira] Commented: (VELOCITY-540) Make local directive part of Velocity engine core

[ https://issues.apache.org/jira/browse/VELOCITY-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681380#action_12681380 ] Nathan Bubna commented on VELOCITY-540: --- I should note that the $macro namespace

[jira] Resolved: (VELOCITY-540) Make local directive part of Velocity engine core

[ 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

[jira] Resolved: (VELOCITY-687) Macro pass by value option

[ https://issues.apache.org/jira/browse/VELOCITY-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Bubna resolved VELOCITY-687. --- Resolution: Fixed Fix Version/s: 2.0 Seems to me that Byron already made the switch

[jira] Resolved: (VELOCITY-697) Add macro default parameters

[ https://issues.apache.org/jira/browse/VELOCITY-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Bubna resolved VELOCITY-697. --- Resolution: Fixed Fix Version/s: 2.0 Byron, i'm marking this resolved, because the

[jira] Commented: (VELOCITY-695) Add comments for directive parameters

[ https://issues.apache.org/jira/browse/VELOCITY-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681385#action_12681385 ] Nathan Bubna commented on VELOCITY-695: --- I think that so long as someone else

[jira] Resolved: (VELOCITY-698) If #stop is specified as #stop(template) then parsing only stops current template rendering

[ https://issues.apache.org/jira/browse/VELOCITY-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Bubna resolved VELOCITY-698. --- Resolution: Fixed Fix Version/s: 2.0 1.7 The #stop(parse) is now

[jira] Commented: (VELOCITY-704) VTL Simplicity - Control objects

[ https://issues.apache.org/jira/browse/VELOCITY-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681415#action_12681415 ] Nathan Bubna commented on VELOCITY-704: --- Ok, not quite done with code changes...

[jira] Commented: (VELOCITY-697) Add macro default parameters

[ https://issues.apache.org/jira/browse/VELOCITY-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681451#action_12681451 ] Byron Foster commented on VELOCITY-697: --- Sounds good, I was leaving it open for any

[jira] Closed: (VELOCITY-695) Add comments for directive parameters

[ https://issues.apache.org/jira/browse/VELOCITY-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Byron Foster closed VELOCITY-695. - Resolution: Fixed Better huu? :) Ok, looks like this is going in, so I'll close it. Change

[jira] Commented: (VELOCITY-698) If #stop is specified as #stop(template) then parsing only stops current template rendering

[ https://issues.apache.org/jira/browse/VELOCITY-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681456#action_12681456 ] Byron Foster commented on VELOCITY-698: --- yea, no need for this anymore. If #stop

#set null in 2.0

In 1.x we have: directive.set.null.allowed = false I think that we should flip that to true and perhaps even remove the option in 2.0. Does anyone out there rely on not being able to change variables to null? Does anyone out there even remember why it wasn't allowed in the first place?

Re: #set null in 2.0

Hi, I think we should simply remove the option since it was really a backwards compatibility hack. Do we have a null object? We should. In fact, as a general rule for 2.0 I propose we just fix this stuff and remove the special casing. (Same issue for escaping of characters, by the way). WILL

Re: #set null in 2.0

On Thu, Mar 12, 2009 at 9:07 PM, Will Glass-Husain wglasshus...@gmail.com wrote: Hi, I think we should simply remove the option since it was really a backwards compatibility hack.  Do we have a null object?  We should. We don't need a null object/keyword. $null works fantastically. Keep it

Re: #set null in 2.0

On Mar 12, 2009, at 18:18 , Nathan Bubna wrote: In 1.x we have: directive.set.null.allowed = false I think that we should flip that to true and perhaps even remove the option in 2.0. Agreed. - To unsubscribe, e-mail: