I just noticed a slight difference between Velocity 1.7 and
2.0+VM_PRESERVE_ARGUMENTS_LITERALS:
```
#macro(mymacro $input)
#set($input = $NULL)
$input
#end
#set($variable = 'value')
#mymacro($variable)
```
Velocity 1.7 prints $variable
Velocity 2.0 prints $input
The reason why it's important is
Changing my vote to -1. I did some cleanup and versionning changes, an
RC2 shall be proposed very soon.
Claude
On 19-10-10 16 h 59, Nate Chadwick wrote:
+1 for release, looked good in our testing
On Sat, Sep 21, 2019 at 11:09 AM Nathan Bubna wrote:
+1 GA
Thanks, Claude!
On Fri, Sep 20,
+1 for release, looked good in our testing
On Sat, Sep 21, 2019 at 11:09 AM Nathan Bubna wrote:
> +1 GA
>
> Thanks, Claude!
>
> On Fri, Sep 20, 2019 at 5:33 AM Claude Brisson >
> wrote:
>
> > The Velocity Engine 2.2 RC1 is available since September 8.
> >
> > Main changes in this release:
> >
>
+1 GA
Thanks, Claude!
On Fri, Sep 20, 2019 at 5:33 AM Claude Brisson
wrote:
> The Velocity Engine 2.2 RC1 is available since September 8.
>
> Main changes in this release:
>
> - New 1.7 backward compatibility flags to mimic 1.7.x
> InvalidReferenceHandler behavior.
> - New runtime.log.track
Works great for me.
[ ] Leave at test build
[ ] Alpha
[ ] Beta
[x] General Availability (GA) nb
Thanks.
On Fri, 20 Sep 2019 at 13:33, Claude Brisson
wrote:
> The Velocity Engine 2.2 RC1 is available since September 8.
>
> Main changes in this release:
>
> - New 1.7 backward compatibility
The Velocity Engine 2.2 RC1 is available since September 8.
[ ] Leave at test build
[ ] Alpha
[ ] Beta
[X] General Availability (GA)
Claude
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional c
The Velocity Engine 2.2 RC1 is available since September 8.
Main changes in this release:
- New 1.7 backward compatibility flags to mimic 1.7.x
InvalidReferenceHandler behavior.
- New runtime.log.track_locations debugging configuration flag which
displays the VTL stack trace in the logs in c