Note that the code you indicated in you first message cannot work
since the {{thymeleaf}} wiki syntax would not be executed.As for the idea in general, supporting as many languages as we can is always interesting. On Wed, Jan 3, 2018 at 11:09 AM, Vincent Massol <[email protected]> wrote: > > >> On 3 Jan 2018, at 09:55, Paul Libbrecht <[email protected]> wrote: >> >> Pug has a java implementation: >> https://github.com/pugjs/pug => java => >> https://github.com/neuland/jade4j > > Thanks Paul. > > Doesn’t seem that active either: > https://github.com/neuland/jade4j/graphs/contributors > > BTW there were several other suggestions in the link I gave: > https://dzone.com/articles/template-engines-review-after-deprecated-velocity > > Pebble, Freemarker > > Freemarker is one that we’ve been wanting to investigate for a long time > already: > https://freemarker.apache.org/ > > https://github.com/apache/incubator-freemarker (again mostly one active > contributor). > > We would need to see what it would bring over Velocity for ex. since there’s > little point to changing if it doesn’t bring advantages. > > Thanks > -Vincent > >> paul >> >> On 3 Jan 2018, at 9:47, Vincent Massol wrote: >> >>> Just important to avoid jumping from one sinking ship to another ;) >>> >>> >>> Definitely. Note that my idea here was more of suggesting exploring some >>> other templating languages that would be initially added as a contrib >>> project, rather than replacing Velocity. But you’re perfectly right, if >>> someone is willing to work on this, we might as well pick the right one. >>> >>> However note that pug is not a candidate since it’s not java-based and is >>> for Node.js. > -- Thomas Mortagne
