[jira] [Commented] (DOXIASITETOOLS-92) upgrade Velocity from 1.5 to 1.6.4

["Michael Osipov (JIRA)" <ji...@apache.org>]

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

Michael Osipov commented on DOXIASITETOOLS-92:
----------------------------------------------

No we are not, I have fixed all ITs inline but one which does not make sense.

I have upgraded Doxia Sitetools to Velocity 1.7 and Maven Site Plugin to 1.7 and ran all ITs:

1. We need to remove all references to the Maven Stylus Skin in all {{site.xml}} because we don't support it anymore. Several failed tests now pass.
2. The last remaining failing IT is {{site-jar}} which says "File[images/h3.jpg] not found in jar archive", since neither Default nor Fluido skin contain this file but only Stylus, we can remove this file from the verify script and all is fine.

If you agree, I will assign this issue to be and proceed as described.

> upgrade Velocity from 1.5 to 1.6.4
> ----------------------------------
>
>                 Key: DOXIASITETOOLS-92
>                 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-92
>             Project: Maven Doxia Sitetools
>          Issue Type: Wish
>          Components: Site renderer
>    Affects Versions: 1.6
>            Reporter: Hervé Boutemy
>
> Velocity 1.5 was released in 2007: http://velocity.apache.org/engine/devel/changes-report.html#a1.5
> 1.6.4 was done in 2010 http://velocity.apache.org/engine/devel/changes-report.html#a1.6.4
> I don't have precise feature in mind, just Velocity Tools 2.0 annoucement tells Velocity 1.6 is required (seems to work well with 1.5...): http://velocity.apache.org/news.html#tools20
> bq. This should be useable as a drop in replacement for Tools 1.4 or Tools 2.0-beta4, with a few minor exceptions. The 2.x series of VelocityTools requires Velocity 1.6 and JDK 1.5+.
> From a first test, actual Doxia templates work with 1.6 but not with 1.7, so perhaps upgrading to 1.6 is a good step before trying latest 1.7



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