You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Tim Colson (Jira)" <ji...@apache.org> on 2021/02/12 18:54:00 UTC
[jira] [Comment Edited] (VELOCITY-933) Spring support for Velocity
[ https://issues.apache.org/jira/browse/VELOCITY-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17283912#comment-17283912 ]
Tim Colson edited comment on VELOCITY-933 at 2/12/21, 6:53 PM:
---------------------------------------------------------------
Hello all!
A long time ago, I happily used Velocity and Struts, and Spring, and Apache Click. We all know Velocity releases paused in 2010, and by 2016, [Spring framework folks decided to remove Velocity from the core.|https://github.com/spring-projects/spring-framework/issues/18368](1)
I check in from time to time(2), and still use Velocity when I need a template engine. Good to see a bit of activity. :)
Probably most devs have moved away from Velocity, so nobody has had the itch to re-add it to Spring. Not having an easy path to Spring Boot integration, would keep devs from looking into Velocity. And if they do, even with recent releases, I see a lot of references to 1.7.
If the Spring integration isn't large or wildly different from the old code, that's great. Lower risk, right? Release it! :)
FYI - I poked around, sharing some observations below -
TL;DR Lots of fiddly bugs; plus I suggest a "HowTo use Velocity with Spring and Spring Boot" as part of the Spring (re-)integration release.
Why a howto doc? Divio guy talks about the influence of good docs (3), especially a getting started tutorial. BTW - I used to love that Velocity had a ~5 min doc for Users and for Devs.(Now, one of the first Dev doc headlines is "Headaches"...oh my.)
!Velocity Search Results.png|width=414,height=332!
Searching for "spring boot velocity" brings up two Baeldung articles – both refer to *Velocity 1.7 and Tools 2.0*, then some code on a Chinese site, and a Stack Overflow Q from 2015 specifically asking (without a good answer) how to setup Velocity with Spring Boot.
Maybe somebody could reach out to Baeldung with an update? I know a lot of Java devs that go there.
!2021-02-12 Vel 2.2 shows 1.7.png|width=465,height=220!
The Velocity site has no obvious Spring related info. The Velocity 2.2 Engine page itself refers to *1.7 as the latest* stable version! Oops! Also…
* Link to "central Maven Repository" - broken.
* Maven Central search for Velocity brings up 1.7 from 2010 and 2.0-beta tools from 2007. Not a good look.(4)
* Wiki link in the nav bar (for help maybe) - broken, no such page
* Description for the Velocity wiki space is "moin wiki backup" - that could use an update. ;)
* Wiki pages have no structure.
:D LOL - I see a [TimColson page|https://cwiki.apache.org/confluence/display/VELOCITY/TimColson] which I cannot edit nor (ideally) remove.
Anybody want to re-grant me permission to at least clean up the wiki, maybe start that Spring Boot howto page?
-Tim
1) Removal also aligned with strategy of not including as many 3rd party libs, and further with opinion that templated pages have been replaced with REST + JS. (Probably true, but not a suitable stack for personalized emails, compared to a template engine.)
2) Made me laugh recently when I had a look at a few recent posts in the dev-list, and saw my name pop up.
3) David Laing of Divio has done a great job explaining the four types of documentation - [https://documentation.divio.com|https://documentation.divio.com/]
4) Yes, I noticed the package names have changed over the years. I don't know why, but at this point, any normal person would have bailed. Path needs to be more direct.
was (Author: timcolson):
Hello gents!
A long time ago, I happily used Velocity and Struts, and Spring, and Apache Click. We all know Velocity releases paused in 2010, and by 2016, [Spring framework folks decided to remove Velocity from the core.|https://github.com/spring-projects/spring-framework/issues/18368](1)
I check in from time to time(2), and still use Velocity when I need a template engine. Good to see a bit of activity. :)
Probably most devs have moved away from Velocity, so nobody has had the itch to re-add it to Spring. Not having an easy path to Spring Boot integration, would keep devs from looking into Velocity. And if they do, even with recent releases, I see a lot of references to 1.7.
If the Spring integration isn't large or wildly different from the old code, that's great. Lower risk, right? Release it! :)
FYI - I poked around, sharing some observations below -
TL;DR Lots of fiddly bugs; plus I suggest a "HowTo use Velocity with Spring and Spring Boot" as part of the Spring (re-)integration release.
Why a howto doc? Divio guy talks about the influence of good docs (3), especially a getting started tutorial. BTW - I used to love that Velocity had a ~5 min doc for Users and for Devs.(Now, one of the first Dev doc headlines is "Headaches"...oh my.)
!Velocity Search Results.png|width=414,height=332!
Searching for "spring boot velocity" brings up two Baeldung articles – both refer to *Velocity 1.7 and Tools 2.0*, then some code on a Chinese site, and a Stack Overflow Q from 2015 specifically asking (without a good answer) how to setup Velocity with Spring Boot.
Maybe somebody could reach out to Baeldung with an update? I know a lot of Java devs that go there.
!2021-02-12 Vel 2.2 shows 1.7.png|width=465,height=220!
The Velocity site has no obvious Spring related info. The Velocity 2.2 Engine page itself refers to *1.7 as the latest* stable version! Oops! Also…
* Link to "central Maven Repository" - broken.
* Maven Central search for Velocity brings up 1.7 from 2010 and 2.0-beta tools from 2007. Not a good look.(4)
* Wiki link in the nav bar (for help maybe) - broken, no such page
* Description for the Velocity wiki space is "moin wiki backup" - that could use an update. ;)
* Wiki pages have no structure.
:D LOL - I see a [TimColson page|https://cwiki.apache.org/confluence/display/VELOCITY/TimColson] which I cannot edit nor (ideally) remove.
Anybody want to re-grant me permission to at least clean up the wiki, maybe start that Spring Boot howto page?
-Tim
1) Removal also aligned with strategy of not including as many 3rd party libs, and further with opinion that templated pages have been replaced with REST + JS. (Probably true, but not a suitable stack for personalized emails, compared to a template engine.)
2) Made me laugh recently when I had a look at a few recent posts in the dev-list, and saw my name pop up.
3) David Laing of Divio has done a great job explaining the four types of documentation - [https://documentation.divio.com|https://documentation.divio.com/]
4) Yes, I noticed the package names have changed over the years. I don't know why, but at this point, any normal person would have bailed. Path needs to be more direct.
> Spring support for Velocity
> ---------------------------
>
> Key: VELOCITY-933
> URL: https://issues.apache.org/jira/browse/VELOCITY-933
> Project: Velocity
> Issue Type: Task
> Components: Engine
> Affects Versions: 2.3
> Reporter: Claude Brisson
> Assignee: Claude Brisson
> Priority: Major
> Fix For: 2.3
>
> Attachments: 2021-02-12 Vel 2.2 shows 1.7.png, Velocity Search Results.png
>
>
> Add a new jar submodule for Velocity Spring support
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org