{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 爷、活的狠高调 的问题《Why Velocity support is deprecated in Spring 4.3?》','https://www.manongdao.com/q-618675.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
And how are we going to use Velocity with Spring after Spring 5.0?
相关问题
- Delete Messages from a Topic in Apache Kafka
- Jackson Deserialization not calling deserialize on
- How to maintain order of key-value in DataFrame sa
- StackExchange API - Deserialize Date in JSON Respo
- Difference between Types.INTEGER and Types.NULL in
It looks like Jürgen Höller wants to get rid of Velocity alltogether, because it "dates back to 2010". Support for it was deprecated in Spring 4.3, and will probably be removed in Spring 5.
https://jira.spring.io/browse/SPR-13795
In the accepted answer from @Olivier Croisier he states that the reason for depracating velocity was that it "dates back to 2010". While this doesn't seem a particularly valid reason to get rid of something (The C language dates back to 1972) that was actually Jurgen Hoeller's reason given in the issue description that Olivier links to!
In further comments added to that issue, that appear after @Olivier Croisier's answer was given, there is further elaboration. It seems Spring wishes to limit the 3rd-party adaptors that they provide to only two implementations and suggest that the other 3rd-parties develop their adaptors themselves.
The impression I get is that velocity was neither popular or modern enough to be selected as one of the two.