22 Jul
2016
22 Jul
'16
8:58 a.m.
One thing that would be nice to have is the custom whitespace filter
that the {{velocity}} macro has: see
http://extensions.xwiki.org/xwiki/bin/view/Extension/Velocity+Macro#HParame…
and
http://extensions.xwiki.org/xwiki/bin/view/Extension/Velocity+Macro+Filter
Basically, Velocity only supports literal whitespace processing, with
every space and newline going into the output, while we like to be able
to indent our sources without padding the output with lots of extra spaces.
On 07/22/2016 02:49 AM, Vincent Massol wrote:
Hi Claude,
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
On 21 Jul 2016, at 17:26, Claude Brisson
<claude(a)renegat.net> wrote:
Hi.
I'm currently working on Velocity 2.0 packaging.
If that's OK with you, I would like to incorporate DeprecatedCheckUberspector.java
into Velocity, but I need a statement from your part to be able to change its licence to
Apache 2.0 (LGPL and Apache 2.0 licences aren't compatible).
Thanks for reaching out. A big +1 from me too. The more we can move to Velocity the
better it is.
By the way, I take this opportunity to tell you
that if there is another specific part of xwiki-commons-velocity that you think should be
integrated on our side, or an important missing feature you'd like to insist on,
don't hesitate. I already integrated VELOCITY-825, for instance, so String->Enum
constant conversions are now handled by Velocity. There may be other important conversion
cases you'd like to see handled.
Ok cool.
On your side, if you see other issues that you’d be willing to integrate let us know.
Thanks
-Vincent
> Regards,
>
> Claude