You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "David Sean Taylor (JIRA)" <je...@portals.apache.org> on 2014/09/12 18:17:34 UTC

[jira] [Commented] (JS2-1306) Update Velocity to 1.6.4

    [ https://issues.apache.org/jira/browse/JS2-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131708#comment-14131708 ] 

David Sean Taylor commented on JS2-1306:
----------------------------------------

I upgraded the 2.2.3 branch to Velocity 1.6.4. Looking into using Velocity 1.7 / VelocityTools 2.0 for 2.3.0...

> Update Velocity to 1.6.4
> ------------------------
>
>                 Key: JS2-1306
>                 URL: https://issues.apache.org/jira/browse/JS2-1306
>             Project: Jetspeed 2
>          Issue Type: Bug
>    Affects Versions: 2.2.0, 2.2.1, 2.2.2
>            Reporter: Joachim Mueller
>            Assignee: David Sean Taylor
>             Fix For: 2.2.3, 2.3.0
>
>
> An issue with velocity 1.6.3 can lead to a 100% CPU loop hang under simultaneous HashMap calls (VELOCITY-718). This is fixed in velocity 1.6.4, which is a drop in replacement for 1.6.3.
> http://velocity.apache.org/news.html#engine164
> The velocity version in the root POM should be set to 1.6.4.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org